That sounds good, for /kbin seems to generally have troubles with federating to the outside Fediverse. For example, formatted posts or posts with embedded links go out as raw Markdown code, implying that everything else can and will parse it, rather than standard Rich Text.
Also, I sometimes see posts from /kbin with a summary (the same as a content warning on Mastodon; I don't know what /kbin uses that field for), but the post in the summary is the same as the summary, only without hashtags which only appear in the summary.
That's a lot of information, I'm personally most excited for the spoiler support and the /sub refinements. I never really see any posts from users I follow because they get drowned out by the magazines I'm subscribed to. So this made me hold back with following users so far.
Subsequent updates will be carried out promptly, so if you encounter any new issues with the site, please mention me.
I wonder if it might be an idea to post a prominent message or banner or similar when you're updating the site, especially for updates that may take longer than a few minutes and/or have the potential to cause longer site outages should something go wrong. That way people would know that any issues they may encounter are due to a planned outage rather than something going on.
I also wonder if it might be an idea to have a means of communicating with users that is not the kbin.social account, but rather something like a Mastodon account. That way if there's a serious problem with kbin.social people can get updates from this alternative Fediverse identity.
So, the banner is something I've been thinking about for a while, but there was never enough time. Now, with more frequent updates, I'll take care of it because it may be necessary. As for the second account, I was thinking more along the lines of a status page, something like https://status.codeberg.org/ because for some, that's the only account on the fediverse.
Random stuff from all over the fediverse
Destacado