I explained this in my post: https://lemmy.world/post/149743
Those communities still exist on this instance, they just aren’t synced. You can see new posts from only lemmy.world users. Any posts/comments you make are not shared within the wider lemmyverse.
Effectively that community is a zombie community on this instance. Just unsub from that community, it’s useless to you unless behave decides to refederate.
The fact that these communities exist to instances that are cutoff from the “true” instance is a horrible UX. There should be a giant “unplugged” overlay signaling that that youre essentially writing to a google doc that is not connected to the internet.
This is where the Lemmy interface could use some work. It should definitely notify users when they are about to post to an instance that is defederated with them and let them know that no other instances will see the post.
Out of curiosity, are lemmy.world mods still able to moderate these zombie communities?
It seems odd that people would be able to post in them when the people who are supposed to handle the communities just aren’t there.
This is the correct answer, lots of people think defederating is one-directional when it’s not. It’s 100% blocked communication both ways, meant to be the nuclear option as a last resort (sadly the lack of other moderation tools makes it a second resort after reaching out to the other instance).
If defederating still allowed any communication, it wouldn’t be useful if a remote instance was malicious and exploiting protocol-level bugs and trying to exploit other instances. Defederating should protect against that too, hence 0 communication whatsoever.
The uni-directional option would be limiting a remote instance, which unfortunately isn’t implemented here.
I read elsewhere that it’s not completely bidirectional when it comes to posts on a third party instance. For example, if lemmy.world and beehaw.org users both post to a thread on another instance that they are both still federated with, lemmy.world users will see the beehaw.org users’ posts, but not the other way around.
I haven’t confirmed if this is true yet though, so maybe someone can correct me if I’m wrong.
Because Lemmy.world is still federated with beehaw. No one on beehaw will see anything you do.
lemmy.world is collectively shadowbanned
We’re basically in a read-only state it seems like
(edit: but apparently there’s more to it than that)
No, we are not getting any Beehaw posts from Beehaw, and nobody outside of lemmy.world can see any of the posts in question.
The only time we see any posts that say Beehaw, it’s because someone from lemmy.world is trying to post there. Nobody on Beehaw, and nobody on any other instance can see them.
Go to another instance and check the Beehaw communities. Posts created from lemmy.world aren’t there.
Because we didn’t de-federate with them. So, if you comment, only other lemmy.world users will be able to see your comment and interact with it.
So does the rest of the Fediverse need to defederate from Beehaw to clean up their sites?
EDIT: Nevermind I can see that if that happened, we wouldn’t see Beehaw users posts in other fediverse servers that both sites are still federated to. It seems like defederating is a messy thing to do.
As others said. But to be more precise, someone on lemmy.world tried to post to !technology@beehaw.org. That post will get sent to BeeHaw but their server will reject it because they’ve blocked lemmy.world.
Other users of lemmy.world can see this post, but nobody else. That’s because lemmy.world knows about the post since it’s own user made it, but every other instance will be looking at BeeHaw’s servers for new posts in that community.
I’m pretty sure the only thing that’s changed is that people on Beehaw won’t be able to see our posts
No, check from another Lemmy instance. Those posts aren’t there.
As the “owner” of a community an instance is responsible for distributing posts made to it to other servers. Beehaw have said they’re not listening to lemmy.world and so don’t distribute posts made by lemmy.world users.
