YSK: You can see which instances your home instance is federated with and which they've defederated/blocked by going to "/instances"
YSK: You can see which instances your home instance is federated with and which they've defederated/blocked by going to "/instances"
For example, you can see this breakdown for Lemmy.world by going to https://lemmy.world/instances
This is so helpful! Thank you!
That list won't show which instances have block the home instance. The blocked list lists only the instances the home instance has blocked, not the other way around.
How does this work exactly? If another instance blocks lemmy.world for example can I still see (but not interact with) content on the other instance, or is it completely invisible?
Basically it works like this:
Instances A, B, and C are federated initially. When a user posts on Instance A, users on Instances B & C can see and interact with the post directly. Any comments they make will be sent back to Instance A as the "home" instance for that content.
Now let's say Instance A decides they don't care for the type of interaction they're getting from Instance C's users and decides to block - or defederate - Instance C.
To users on instance A, nothing changes other than new posts and comments from users on Instance C will no longer show up. To users on Instance B, nothing changes other than new comments from users on Instance C won't appear in posts they interact with on Instance A. However, for Instance C, things are suddenly branched.
On Instance C, any posts that were created prior to defederation still exist in Instance C's record. However, any comments that users on Instance C commit to those posts will no longer be distributed to users on Instances A or B, because Instance A maintains the "primary" record of the post. Similarly, Instance C's users will not receive updated comments from users on Instance A OR Instance B, because again, Instance A is what determines which comments appear in federated instances. Furthermore, new posts created on Instance A will no longer show up in users' feeds on Instance C. From the moment of defederation, Instance C's copies of all posts on Instance A are now distinct, and the only new comments or updates they will receive will be from local users on Instance C.
Funny finding skinheads.social on that list there. Is federating automatic, requiring an opt-out to separate, or did an administrator see that name and go “yup, we want people to see skinhead content?”
If I understand it right, federation happens automatically when someone from a new instance interacts with the home instance, or someone from the home instance searches out the new instance.
It looks like that site might be running with the British use of "skinhead" and not the U$ use. It was a progressive punk/ska subculture before it became used as a white supremacist thing in the U$.