So my understanding is that KBin.social is now gone from the internet for the indefinite future. Ernest, who meant well, simply could not keep up with the demands due to his personal life and the development issues that were cropping up all the time. Let me get ahead of any replies and say that it's perfectly reasonable to shut down a large instance if it's taking up your time and money or becoming a burden on your personal life. Personal health should always come before a bunch of random dudes/dudettes that happen to be on the internet. Additionally, it's a good reminder that developing software while also maintaining a large instance probably isn't a good idea and that you should probably make sure you're taking a reasonable amount of work off your plate.
But I can't help but feel like there's another story here regarding the potential risks of the fediverse: Admins need to be ready to migrate ownership to others who are willing to take on the financial or user account management burden. Additionally, there should be a larger focus on community migration features for more flexibility to sudden instance losses.
I managed a community that had partially migrated to Kbin after the great reddit exodus last year and managed to continue to admin said community up until a few months ago when Kbin's service became very very spotty. I understood Ernests' particular dilemma so I was willing to give it a month or two to figure out what actions I needed to take to migrate the community again, but enough time has passed now that I am no longer confident that Kbin will return to even a read-only, moderator only state. This means that whatever community I had there is now completely out of my control and the users might not know why posts have stopped entirely. Basically, I have to start from the ground up which might be OK but I'm not particularly keen to start it all over right now.
So this is basically a plea to the admins out there: If you are having trouble with management and need to stop, could you please give the community a vocal heads up so that whatever subcommunity happens to form on your site has some means of migrating? Additionally, software out there should have more policies for community migration, whether that's lemmy or mbin, as we never know when it might be necessary to migrate to a new domain under different ownership. Lastly, if there's an option to give ownership to others in the community, please consider it as it would really help the fediverse if admins were willing to migrate domain and databases to other users who are willing to carry the torch.
That's it from me for now, thanks for reading this minor rant. 🤙
You’ve highlighted what is definitely a major problem with the Fediverse - all it takes for you to lose all the hard work you’ve done building up a community is the person running a server to pull the plug with no warning.
I loved kbin social - I started out on there, and only moved over to lemmy because it was getting too erratic and it was impossible to find out what was going on. Being able to move is a great thing, but if you miss your window to move, you’re SOL.
Admins definitely need to be willing and able to have the reins over to someone else if it’s getting to be too much, or to at least let people know in advance if they’re planning to shut down. Communication is key.
This also shows the even more important lesson: if you want to maintain a community you also have to be responsible about digital community sovereignty. Set up your own instance, or at least set up your own webpage (even a Neocities one) that is kept updated with information about where the active community and any alternatives / mirrors are.
We are coming out from reddit yet still have to fully learn the lesson about renting our existence on someone else's server. (And, to be fair, fediverse development as a whole should be helping with that: in the least migrating user accounts should be as easy as "export to file" → "import from file").
This is an excellent point that I thought about when a previous community I was active in got shut down on the ml instance due to some admin whims. Since then, for the two communities I run, I have an external wiki that I maintain with things like complete rules or an index of past weekly discussion threads, etc. These wikis are set up on a VPS that I am responsible for, independent of the host instance of my communities.
ani.social and the admin, @hitagi@ani.social, has been excellent, and the instance is a logical place for anime/manga communities. I have also tried to keep up donations to keep the server running, but people's lives change, not always by choice. Having some form of communication independent of the lemmy instance makes sense for those scenarios, if for nothing else except for communicating a migration to a different instance.