Skip Navigation

Blocked vs defederated instances

Is "defederated" instances a synonym for "blocked" instances? are they read-only without interactions or they can't even be read from other instances?

E.g: if beehaw is defederated can I still browse its subs from lemmy.world?

4
4 comments
  • Not quite. Blocked means you won't see any of their posts, it's something users can do.

    Defederating is something instance admins can do. Defederating from an instance means everyone in your instance can't see their posts, and they can't see ours from here on out.

    Here's where people get confused: even after defederating, their communities and all of their older content still exists here. But, you can think of them as "dead" communities. Anything you post there won't be federated, meaning only your instance will see what you post there. All other instances won't see your post on a community you've defederated with, so it's important to stop posting there and instead post on communities you're federated with.

  • You can browse outdated copies of its communities, but no new comments or posts will appear. You can comment on old posts, or make new posts, but the only people seeing them will be users on your instance.

  • Is there a way to block an entire instance as a user? There are some instances that seem to cater to communities that I have zero interest in, Abe instead of blocking each community, Id rather block the whole instance