I can’t see any comments from beehaw users, but the new posts from beehaw subs still show up when I sort the frontpage by “All” communities.

Am I miss understanding something here?

  • TheOneCurly@lemmy.theonecurly.page
    1·
    1 year ago

    Users on lemmy.world still have a “shadow” version of the beehaw communities on lemmy.world that would normally be synced but isn’t anymore. Users on lemmy.world can post to that community and it can be seen by other users there but that post doesn’t go back to beehaw or anyone still federated with them.

    • positiveWHAT@lemmy.world
      1·
      1 year ago

      So just the interactions with the posts are blocked, not the posts themselves? I find it a bit weird, but OK.

      • chaorace@lemmy.sdf.org
        0·
        1 year ago

        It means that beehaw can’t “hear” anything coming from lemmy.world.

        When you write a comment, it gets saved to lemmy.world (or whichever home instance you’re currently using). The lemmy.world instance then broadcasts your comment out to the Fediverse. Normally, this causes other instances to see your comment and save a copy locally, which is how it’s possible to see your comment on other instances. Because Beehaw ignores lemmy.world, their instance ignores the broadcast containing your comment. It’s never saved to Beehaw which stops the users logged in over there from ever having a chance to see it.

        In addition to ignoring lemmy.world, Beehaw is also excluding lemmy.world from it’s own broadcasts. So, if someone goes and creates a post on Beehaw, the lemmy.world instance will never get told about it thus stopping those logged into lemmy.world from ever knowing it existed. You simply can’t interact with something that doesn’t exist, even though lemmy.world technically isn’t trying to stop you.

        What you’re seeing here is the overlap between these two effects. The lemmy.world instance knows of old posts that exist on Beehaw, because Beehaw was still talking to lemmy.world back then. Then you as a user on lemmy.world can see the post and write a comment on it, since your comment lives on lemmy.world. Finally, lemmy.world tries to tell Beehaw about your comment and gets ignored, preventing anyone on Beehaw from ever knowing it existed.

          • chaorace@lemmy.sdf.orgEnglish
            2·
            1 year ago

            The Beehaw admins saw a disproportionately high amount of rule breaking coming from lemmy.world. They posted about it and specifically said that the issue was a combination of lemmy.world’s huge userbase and open-door signup policy.

            • polygon@kbin.social
              1·
              1 year ago

              Also Beehaw bills itself as a “safe and inclusive space” which is huge bait to a certain type of internet scumbag. It makes Beehaw a large target for trolling and abuse. Without tools to deal with this I can see the logic in just defederating until moderation can get better. They’ve also been in contact with the instances they’ve defederated from and are discussing ways to move forward because everyone realizes this isn’t an ideal situation.

              I can sympathize with why they felt this was their only option, but on the plus side, this situation might just spur development of real moderation tools that are desperately needed for anyone running a Lemmy instance. Some people want to hate on Beehaw for their decision but honestly we might all be benefiting from it in the long run.