this post was submitted on 15 Jun 2023
1 points (57.1% liked)
Asklemmy
43892 readers
898 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You're seeing a cached version of the post from before defederation. Those comments only exist on your instance and the post will drop off your feed soon enough.
Let me see if I understand this correctly:
If there's community C from instance A, and it's visible to instance B, then there's a "view" of C@A that B users can see. We can say that B "sees" C@A; when B users "look for" C@A they see this view of it.
So long as A and B federate, those stay in sync, and the moderators of C@A can control what B users see when they look for C@A.
But if A and B stop federating, then the view of C@A from B becomes decoupled from the view of C@A from A.
And this stops the A moderators from having any effect on posts to (the B view of) C@A from B.
Users on B still see C@A, but their view is onto an unmoderated C@A that only contains traffic from B.
So, any community that is seen and then defederated, becomes an unmoderated space on the seeing instance.
Am I missing something? That seems like a pretty bad bug.
Kind of...
So lets say there is a group called Group A on Instance A. And there is a user called User B on Instance B that is subscribed to Group A.
Then Instance A defederates from instance B. At this point, instance B still has cached copies of the stuff that happened in Group A before defederation. However, they won't see any new content, and crucially, even though they can still see a cached version of Group A, if they try and post to it from Instance B, won't be boosted/relayed/propagated by Group A, so no one else will see their content.
Edit - The exception might be that other users on Instance B that were users of Group A, may see new content generated by Instance B users, though I'm not sure if that's the case
Yeah, that's exactly what I mean. The people on instance B who look at the "C@A" community can still post; their posts won't propagate to other instances but they will see each other's messages, but nobody but the instance B admin will be able to moderate those messages.
IRC and Usenet both have had similar situations.
That's not a bug though, that's just how federation works
It's a corner case that could maybe be handled differently in ways that wouldn't have the surprising consequence, though.
B can defederate from A if it wants to prevent these bastard communities.