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?”
just kbin.social. all kbin instances federate with everyone and block no one by default but instance owners can intentionally defederate/block if they so choose. afaik kbin.social's policy is to not defederate/block (at least the admin here hasn't mentioned anything yet). I haven't heard of other kbin instances defederating at all though, but most are so small to not even be noteworthy.
First, because some instance's block list indicates unwillingness to see anything beyond their little world.
Second, because in some (only only some) blocklists, there are links to some actual shitty people who I wouldn't think actually have the capacity to run a server.
In the last few days there's been quite a fuss about some instances storing insulting jokes and whatnot, but maaaan that's honestly nothing compared to what else is out there.
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?
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.
Thanks, very helpful! What about posts from instance B and comments in instance B post? I'm assuming instance B users can see both comments from instance A users and instance C users but for them (instance A and C users), they can only see their respective instance users' comments and instance B users' comments?
The most important part of the federation process is played by whichever instance hosts the original post. They’re the hub and all other instances are the spokes.
So once Instance A defederates from Instance C, nothing Instance C users add to posts hosted by Instance A will be added to the master manifest. Basically, everyone is updating Instance A’s copy of the post, and that copy is then being redistributed to all other federated Instances.
Once Instance A defederates from Instance C, the only time their users will interact from that point forward is on a mutually federated instance. Both communities can comment and interact on a post hosted by Instance B.
I didn't know that, read a bit of that wiki entry, fuck them majorly. I only shared that link because I knew that it works and someone else shared it on here before because of the exploding-heads stuff that was going on.
Add comment