I thought I understood, but I still have Beehaw content in my feed, so I guess I don’t understand after all… Can someone dumb it down for me?
I thought I understood, but I still have Beehaw content in my feed, so I guess I don’t understand after all… Can someone dumb it down for me?
So when an instance is blocked, it means users on the blocked instance will no longer be able to see that instance’s content. For example, beehaw.org has now blocked lemmy.world. However with the way federation works, the content from beehaw is cached on lemmy.world servers. So you can only see what has already been cached; there will be no updated content on any existing cache.
Edit: here’s a recent post from kbin.social going into further detail on how federation works.
Wrong.beehaw blocked lemmy.world. lemmy.world has not blocked beehaw. lemmy.world will continue to get content from beehaw. beehaw has stopped all content from lemmy.world from comming to beehaw.lemmy.world accounts can still see new post and comments from beehaw but no comments will be responded to by behaw users because they cannot see lemmy.world post or ocmments.nvm looks like their content did stop coming through.
Wrong wrong. You won’t get any new content hosted from beehaw.org
You will see beehaw users in other instances, but you won’t be able to see anything new on BeeHaw communities, like /c/[email protected]
I’ve already updated my comment and crossed it out.
We don’t get posts from their instance, only those that are posted by lemmy.world users, and those posts are also exclusivly ours.
Hmm, maybe your right. I’ll add a edit.