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. ๐ค
Well that is certainly relevant news! And sad to see too.
So long for the kbin family of platforms then (seriously, harsh to say, but so long as this is representative, I reckon that spells the end of it on the fediverse).
@maegul @fediverse yeah...in interest of fairness, I did ask him for a comment on the situation before I went public with the information, but he completely ignored me so after 3 days I had to make a public statement on it.๐
Me asking him: https://social.beaware.live/@BeAware/112914020692638023
Me making it public: https://social.beaware.live/@BeAware/112922757724465742
I can only do so much "investigating" before making it known.
Very much appreciate that you did this (and this follow up too)!!
But lunduke is a fairly known entity by now I think. I recall many getting weird about him and his business-y linux persona shtick even before the transphobia stuff started. So while it's completely fair to give Melroy a chance, providing a helping hand on mastodon almost just speaks for itself.
And I'm not even saying that mbin necessarily should "die" because of this, just that it likely reflects an attitude that will not work well on the fedi over time, and probably justifiably so.