MoogleMaestro

https://lemmy.zip/u/MoogleMaestro

Public Key

npub14ghpqvgfnan4urstuwwq785a6a50x5t6zf6e3ym0hw4u8flvkt4qmu897m

NIP-05 Address

mooglemaestro_at_lemmy.zip@momostr.pink

Profile Code

nprofile1qqs25tssxyye7e67pc9788q0r6waw68n29apyavcjdhmh27r5lkt96sprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyqqywzc7v

Publishing to

relay.momostr.pink

Author Public Key

npub14ghpqvgfnan4urstuwwq785a6a50x5t6zf6e3ym0hw4u8flvkt4qmu897m

Show more details

Last Notes

2024-08-08 22:19:52 UTC

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. 🤙