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. ๐ค
yeah I guess its like ernest created kbin and that is something but this guy forked it as part of a multiperson run project. I feel like it should be like technical creator or something.
@HubertManne but if he has the merging powers, it doesn't matter because the buck stops with him on what's implemented.
wait so mbin is all down to one person controlling it? No one else can manage the version control? That just makes it the same as kbins boat then!
@HubertManne pretty sure that's how every project works in terms of merge requests...no? Even mastodon can only have merges approved by Eugen Rothko.๐คทโโ๏ธ
certainly not in companies. pull requests can be authorized by a set of rules which is usually some automated checks and review by X number of members of the group who owns it.
@HubertManne
Well...this is not a company. However, after reviewing the github. It does seem like there's at least one more who can approve merges
@fediverse
honestly only two is pretty scary. they really should have half a dozen
No. I gave others full merge rights. Look at my C4 document: https://github.com/MbinOrg/mbin/blob/main/C4.m
I don't want a single point of failure. I don't want to be the bottleneck of a community project like this. Hence any person can become owner if they contribute enough inline with the guidelines.