Was there recently a kbin backend change? I haven’t been able to see kbin posts all week but they’re populating now.
It might be related to this:
https://kbin.social/m/random/t/134102/Blocking-instances-to-clear-the-500k-queue#commentsToday kbin.social is blocking a huge list of domains just to get federation working again.
The reason for this temporally block is not to defederate, but rather to get the large backlog of 500k messenger queue processed again. Anyway, this does mean that kbin.social is federating again with other instances.
This is a temporary measure. Several users / developers are looking into how to better optimize the failed message queue, as we speak. Hopefully Ernest has eventually time to dive into solutions as well instead of workarounds, once his instance is migrated to Kubernets. See my preview thread: https://kbin.melroy.org/m/updates/t/4257/Kbin-federation-issues-and-infra-upgrade
This is super helpful, thanks!
Maybe to avoid repeated questions like this there should be a set place on at least the home page to have a notice of potential issues. Sort of like a status of the general system, since there’s a lot more going on under the hood than just a webpage loading. As far as real estate for such, right top under the settings seems fine for a line or so of text or something.
And it turns out that’s exactly what is done. Just saw a notice about a planned outage tomorrow posted. I do think it should be at the top and not below all the subscription/magazine info though, and maybe a bit more “flashy” with an obvious border contrast or something.
Another edit: Okay, someone is either reading this and liking the idea, or it’s total coincidence and they figured out it would look better.
