this post was submitted on 11 Jun 2023
2 points (100.0% liked)

Asklemmy

43821 readers
856 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

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?

top 11 comments
sorted by: hot top controversial new old
[โ€“] pootedesu@latte.isnot.coffee 3 points 1 year ago* (last edited 1 year ago) (3 children)

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.

Those are exactly my thoughts. Migration and merging communities will be important sooner or later

[โ€“] RadDevon@lemmy.ml 1 points 1 year ago

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.

[โ€“] oxideSeven@sh.itjust.works 1 points 1 year ago (2 children)

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

[โ€“] maniel@lemmy.ml 2 points 1 year ago

That's what federation means, not really peer to peer

[โ€“] bdonvr@lemmy.rogers-net.com 1 points 1 year ago (1 children)

It doesn't really. I'm viewing this post from my instance, which has saved a copy of this post from lemmy.ml

Me viewing this post doesn't hit lemmy.ml at all, although making this comment will.

[โ€“] oxideSeven@sh.itjust.works 1 points 1 year ago (1 children)

Ah, I misunderstood then.

What happens if lemmy.ml is down?

[โ€“] aponigricon@beehaw.org 1 points 1 year ago (1 children)

All the users and communities registered there will cease being able to connect to the rest of the network, but the data should still be cached on all the other servers.

[โ€“] tiwenty@lemmy.world 2 points 1 year ago (1 children)

The keyword is "cache". Lemmy doesn't guarantee the cache, so if an instance X would go down permanently, you would eventually lose this data.

[โ€“] aponigricon@beehaw.org 2 points 1 year ago

My presumption was that with over 200 instances, maybe over 1000 in the near future, all the old data should be collectable in theory without loss. But you're right, there's no guarantee of this.

[โ€“] LucidDaemon@lemmy.ml 2 points 1 year ago

Just my thoughts from a random user

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