146

For example, you can see this breakdown for Lemmy.world by going to https://lemmy.world/instances

all 34 comments
sorted by: hot top controversial new old
[-] ClassyHatter@lemmy.world 11 points 1 year ago

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.

[-] EtherealZucchini@lemmy.world 6 points 1 year ago

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?

[-] CthuluVoIP@lemmy.world 23 points 1 year ago

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.

[-] AnonymousLlama@kbin.social 4 points 1 year ago

Cheers on the detailed explanation. At some point we should get a GIF going to visualize it, it'll be much easier to explain to new people

[-] mauve@lemmy.pro 3 points 1 year ago

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?

[-] CthuluVoIP@lemmy.world 2 points 1 year ago

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.

[-] G59@lemmy.world 3 points 1 year ago

Thanks for the explanation!

[-] genoxidedev1@kbin.social 2 points 1 year ago

You can view which instances blocked lemmy.world (as an example but any lemmy based instance works and others may work too) on this site using the field below "Enter a Domain"

[-] Kierunkowy74@kbin.social 5 points 1 year ago
[-] genoxidedev1@kbin.social 2 points 1 year ago

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.

[-] WhoRoger@lemmy.world 2 points 1 year ago

I don't know if an instance has an active way to know some other has defederated from it.

[-] Gullible@lemmy.world 5 points 1 year ago* (last edited 1 year ago)

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?”

[-] Otome-chan@kbin.social 12 points 1 year ago

Federation is automatic unless your instance is using a whitelist setup.

[-] megsmagik@feddit.it 2 points 1 year ago

In Europe we have red skins (leftists) and apolitical skins, so being a skinhead is not equivalent to being a nazi (although we also have naziskins unfortunately)

[-] WhoRoger@lemmy.world 4 points 1 year ago

The link is also down at the bottom (at least in mobile version}.

I've been lookin at some block lists just earlier today. I have to fess that some instances' block lists make me uncomfortable.

[-] spiritedpause@lemmy.world 3 points 1 year ago

Ah didn't even notice it at the bottom, good catch!

What makes those block lists uncomfortable for you, genuinely curious?

[-] WhoRoger@lemmy.world 5 points 1 year ago

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.

[-] postscarce@kbin.social 2 points 1 year ago

Is there anything like this for kbin?

[-] AnonymousLlama@kbin.social 2 points 1 year ago

Can't find anything like that on kbin but it would be super handy to have that somewhere accessible (maybe in the footer). I'll ask the dev chat

[-] gaun@kbin.social 1 points 1 year ago

Couldn't find any info on this. Curious too

[-] Otome-chan@kbin.social 0 points 1 year ago

kbin federates with everyone, and blocks no one :)

[-] spiritedpause@lemmy.world 2 points 1 year ago

Is this referring to kbin.social, or do all kbin instances work this way?

[-] Otome-chan@kbin.social 1 points 1 year ago

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.

[-] PixxlMan@lemmy.world 1 points 1 year ago

That's identical to Lemmy...

[-] genoxidedev1@kbin.social 2 points 1 year ago

You can use this sites reverse search function as well, but I do not know of an alternative for kbin

[-] Kierunkowy74@kbin.social 1 points 1 year ago

Not implemented yet.

[-] markovianparallax@lemmy.world 2 points 1 year ago

This is so helpful! Thank you!

[-] iconic_admin@lemmy.world 0 points 1 year ago

That’s a lot of instances.

this post was submitted on 29 Jun 2023
146 points (99.3% liked)

You Should Know

33254 readers
397 users here now

YSK - for all the things that can make your life easier!

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)


Rule 1- All posts must begin with YSK.

All posts must begin with YSK. If you're a Mastodon user, then include YSK after @youshouldknow. This is a community to share tips and tricks that will help you improve your life.



Rule 2- Your post body text must include the reason "Why" YSK:

**In your post's text body, you must include the reason "Why" YSK: It’s helpful for readability, and informs readers about the importance of the content. **



Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.



Rule 4- No self promotion or upvote-farming of any kind.

That's it.



Rule 5- No baiting or sealioning or promoting an agenda.

Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.



Rule 6- Regarding non-YSK posts.

Provided it is about the community itself, you may post non-YSK posts using the [META] tag on your post title.



Rule 7- You can't harass or disturb other members.

If you harass or discriminate against any individual member, you will be removed.

If you are a member, sympathizer or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people and you were provably vocal about your hate, then you will be banned on sight.

For further explanation, clarification and feedback about this rule, you may follow this link.



Rule 8- All comments should try to stay relevant to their parent content.



Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.



Rule 10- The majority of bots aren't allowed to participate here.

Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.



Partnered Communities:

You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.

Community Moderation

For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.

Credits

Our icon(masterpiece) was made by @clen15!

founded 1 year ago
MODERATORS