this post was submitted on 11 Jun 2023
44 points (100.0% liked)
Asklemmy
43402 readers
904 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!
- Open-ended question
- 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.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To get serious about distribution, I think there needs to be a few features implemented;
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...
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.
Ah, I misunderstood then.
What happens if lemmy.ml is down?
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.
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.
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.
Media from users of lemmy.ml won't load. You wouldn't be able to subscribe to communities on lemmy.ml. But I think every other instance would show cached data and hold any new comments/posts/votes to sync when lemmy.ml comes back up. I'm not sure how long that cache is kept.
That's what federation means, not really peer to peer
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.
Those are exactly my thoughts. Migration and merging communities will be important sooner or later
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.
I think we want communities to spread out more than users.
Unfortunately if the users are there then they create the communities. So really people just need to spread out.
Migrating means losing a few things you've made or commented on. We're so young that shouldn't be such a big deal yet though.
This l load balancing will have to be automated sooner or later (sooner hopefully) because it's gonna be problematic...