307

Beehaw defederating effective immediately from lemmy.world and sh.itjust.works (beehaw.org)

submitted 2 years ago by gary@lemmy.world to c/lemmyworld@lemmy.world

286 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] NotInTheFace@lemmy.world 4 points 2 years ago

So what does defederation mean in practice? I can still see communities on beehaw im subbed to. Is it just that I won't see new ones? Or that I can't search/comment on them?

[-] Da_Boom@iusearchlinux.fyi 5 points 2 years ago* (last edited 2 years ago)

Ok so Lemmy instances can decide to disconnect from other instances.

We have instance A, instance B and instance C

initially all 3 are interconnected or "federated with each other" - any member of any instance can see the communities and users from any other instance.

Suddenly something happens that makes instance A defederate with instance B

So now instance A cannot see and participate with the communities and users of B and vice versa. However instance C can see and participate in the communities of Both

So in terms of beehaw vs lemmy.world I would be on instance 3 - I can see and participate both, their defederation from each other doesn't affect you, it only affects the users of beehaw or Lemmy.world

EDIT:

I just realised your in lemmy.world. huh weird... Maybe it takes a while for the defederation to settle, or maybe it makes it a one way communication.

EDIT2 I might be wrong, see this post

lemmyworld@lemmy.world/t/22361/-/comment/96933

[-] edgerunneralexis@dataterm.digital 2 points 2 years ago

So in terms of beehaw vs lemmy.world I would be on instance 3 - I can see and participate both, their defederation from each other doesn't affect you, it only affects the users of beehaw or Lemmy.world

This aspect is really crucial for people to understand, so I wanted to emphasize it. This is what gives the Fediverse it's hyper free nature, where if you don't like which instances your instance has chosen tp block, you can always switch to a third instance and have access to both your old instance (thus solving the network effect) and the new one (thus giving you freedom of association). This sort of connected-by-default design choice (I.e. using blacklists instead of whitelists) is also crucial for maintaining the general interconnectivity of the network thats crucial to its functioning.

load more comments (2 replies)