From this post (https://sopuli.xyz/post/15865566) on !AskMbin@fedia.io
It’s very likely related, but we also figured out that both of debounced’s (the admin of kbin.run) accounts on GitHub and Matrix were deleted last night. So there is a possibility that kbin.run is no more.
So I have backup accounts on fedia.io and piefed.social
But when I left spez’s site for the fediverse, I recreated some lost content (while it was still fresh in my head) and added a bunch of new content to kbin.social - AFAIK with ernest MIA and no way to reach an actual admin of kbin.social my new content is now gone.
That was a very discouraging experience. Since then I decided I wouldn’t return until I could set up my own single-user instance - as owning and controlling my own instance largely means I always have a copy of my content, no matter what happens elsewhere.
I wish piefed.social (which only fully opened this year in Jan IIRC) had been around earlier. The lead developer of piefed is really helpful and responsive, and created a lot of documentation on how to run your own instance of pyfedi - including how to set up your own at-home instance via something like ngrok. Basically you get a HOWTO guide on how to do this. Compare with the complexity of getting a Kbin instance up and running in the early days…
Piefed is great indeed
Ok. I have to ask: how many instances will have to go down before the majority of you drop the “you can always hop around to the next one” mentality and start thinking about ways to make the whole ecosystem more mature and professional?
to make the whole ecosystem more mature and professional?
Feel free to hire the devs?
You can and should fund the developers as much as possible , but I am talking about paying for the work done by the instance admins and moderators.
Oh fair point.
Feel free to hire the admins then!
Wait, that might have come out wrong…I am one of the admins. Should I hire myself?
Pros: you get to be your own boss.
Cons: you get to be your own employee.
Is there a solution to make the whole ecosystem mature and professional?
Certainly having everyone on one instance isn’t the way to go.
Implement OpenID? Or logging in with web3 (blockchain)? Or maybe account backup on google drive?
Any solution is better than no solution
Is the problem account making or data having persistence/backups?
Or is the issue having an account on service A, service A dieing and then when you create an account on service B you have to start over again, so we need to improve account portability?
I guess I also wonder… Is that a real problem for Lemmy? For Mastodon where you follow users sure, but does anyone care about their Lemmy account?
Is the problem account making or data having persistence/backups?
Ideally both issues should be fixed.
Personally I don’t care much about old posts that nobody reads anyway. But my nick, settings, subscriptions, avatar, and block list are important.
So perfect solution should be ability to log in from any instance, not just the one I made my account on.
Lemmy allows to export and import those in one click. Does Mbin also support this?
Can I export it from an instance that doesn’t exist anymore?
Oof. Worst way to go. I mean, doing so for personal accounts is fine but that’s a lot of collateral in form of the users there. People always say to spread out over instances, but then shit like this happens. Most users don’t want to run from one instance to another because the admins decided to stop (or due to other issues with them).
I guess that explains the 500s here on Fedia?
The question is when fedia does the same? It’s as if these instances were hosted by extremely unstable people.
@Blaze@sopuli.xyz A sad thing is, that even if MBin had account migration implemented, it wouldn’t really help, as it just got down without a notice or a warning
Oh indeed
