From this post (https://sopuli.xyz/post/15865566) on [email protected]
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.
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?
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?
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?