There's a significant amount of discussion surrounding the issue of lemmy.ml servers reaching their maximum capacity. As someone who already has an account on lemmy.ml, what actions can you take?
Are the registry procedures causing the problem? Since most of my communities are on lemmy.ml, wouldn't I still be using lemmy.lmβs bandwidth? Or is it more crucial to ensure that the communities are distributed more evenly across different instances?
To get serious about distribution, I think there needs to be a few features implemented;
User migration. Allow people who find themselves on an overstuffed server to migrate to a different instance
Community grouping / merging. If there are multiple communities for the exact same thing, allow the mods to group them or merge them to not fracture the user base
User data import / export or cloud backup to a personal provider. If one day your server instance just disappears, it would be nice to know I have a backup of my user data, subscribed communities, saved posts and comments, and maybe a way to relink to my old posts and comments across the fediverse.
Just a few ideas I was thinking about that could possibly help users move around.
I find it strange that anything lives on a single server at all. It's wasting one of the best parts of being peer to peer. Redundancy. Every server should just be sharing the ultimate load and hosting parity so nothing can be truly lost when someone decides they're done with their side project...
I would add to this community migration, which will be important as instances start going offline. User migration is great, but, whereas on Mastodon, the content lives on the user, I believe here it lives on the community.
Yeah. I like being able to join an instance. But I would really like to be able to backup my profile and to be able to transfer it in the future. It would be ideal to be able to just spin up a raspberry pi, and transfer my account to it at some point.
Have communities work similar to how RAID works with drives. It spans across multiple trusted instances, with data mirrored or striped to each. If one goes down, a new instance could become trusted and have the data rebuild on that instance. This would create redundancy and prevent one instance from becoming the main or default.
Allow similar with user accounts or allow instance migration.
Yeah, the faster Lemmy will figure out an account migration the better, i applied for Lemmy.ml account before I've noticed the overload post, now I'm stuck with an intense that's a bit more laggy than I like