• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle
  • >If a server moved their domain they had to have a way to broadcast the name change to all the other instances.

    even if lemmy had a way to do this, doing it for all the users at lemmy.ml would create a large load of federated network traffic between instances, and at the level of a single instance it would cause a lot of database changes (I’ve heard that the sql schema for lemmy isn’t very optimized).

    also, as activitypub doesn’t prioritize synchronization (unlike git and matrix), there could be a lot of desynchronized state, with the name change of users reaching some instance but not others.

    it would be interesting if lemmy.ml really went the clean slate way (and I think the original intention of the devs in running that instance was just to test their code, not to have it become a “flagship” instance), it would sure showcase a valuable lesson in the fediverse…that you shouldn’t rely too much on big instances (there is no huge facebook/twitter/reddit-like thing here).










  • here are 2 more websites you can find information from:

    - https://jointhefediverse.net/ explains things in a simple way. I especially like the analogy with email, and I’d add: just like you aren’t able to login to gmail and outlook with the same username (email address) and password, you can’t login to a fediverse instance with your credentials from another one.
    - https://fediverse.party/en/fediverse/ offers a more technical overview, giving you a bird’s eye view of the fediverse by listing the major fediverse platforms and protocols (yes, activitypub used by lemmy/kbin/mastodon isn’t the only protocol in the fediverse, there are others…)