My home instance was kbin.run, and when I found debounced (its admin) was an Mbin maintainer/contributor it made me feel good about the lifespan of the instance. Now I don't feel so good… if they dipped without any warning, so can you.

And they did this a few weeks after they put up a "how is my driving?" check-in post about how users felt about their server running, and I said it was going well… pretty sure I also said something about being grateful they were long-running, and talked on other places on the Fediverse about how reliable kbin.run was… all signs pointed to the instance having longevity.

Wonder if they just got hacked or something, because it really was out of nowhere, with no warning signs like Ernest had.

Kind of upset because I don't mind hopping accounts, but I had a magazine there, !otomegames@kbin.run. I had just started it new a few weeks ago, moving from its longer-lived iteration on kbin.social because I was unaware kbin.social was down. And now if debounced does not come back I'll have to make yet another new version of the community. Does not set a good precedent, "will I have to put up with constant new versions to follow this community?" The most appropriate place would be ani.social but I'd also probably have to make yet another Lemmy alt to mod it properly—things like reports do not seem to federate properly unless your account is on the same instance as the community you mod. And I really do not want to give Lemmy more users at the expense of Mbin. Lemmy is already the big guy, and we want more diversity on the Fediverse. So I can probably just remake it on whatever Mbin instance I end up on.