Like many, when the recent defederation went down, I decided to create a couple other logins and see what the wider fediverse has had to say about it.

I’ve been, honestly, a bit surprised by the response. A huge portion of people seem to be misidentifying communities as belonging to “lemmy” as opposed to the instances that host them. I think a big portion of this seems to be a fundamental misunderstanding of what this software is, and how it works.

For example, lemmy.world users are pissed at being de-federated because it excludes them from Beehaw communities. This outrage seems wholly placed in the concept that Beehaw’s communities are “owned” by the wider fediverse. This is blatantly not how lemmy works. Each instance hosts a copy of federated instances’ content for their users to peruse. The host (Beehaw in this example) remains being the source of truth for these communities. As the source of truth, Beehaw “owns” the affected communities, and it seems people have not realized that.

This also has wider implications for why one might want to de-federate with a wider array of instances. Lets say I have a server in a location that legally prohibits a certain type of pornography. If my users subscribe to other instances/communities that allow that illegal pornography, I (the server admin) may find myself in legal jeopardy because my instance now holds a copy of that content for my users.

Please keep this in mind as you enjoy your time using Lemmy. The decisions that you make affect the wider instance. As you travel the fediverse, please do so with the understanding that your interactions reflect this instance. More than anything, how can we spread this knowledge to a wider audience? How can we make the fediverse and how it works less confusing to people who aren’t going to read technical documentation?

  • prlang@beehaw.orgEnglish
    9·
    2 years ago

    My understanding is that people from Lenny.world can still “use” behaw by subscribing to communities and commenting on posts, but people on Behaw just can’t see them. Is that not how it works?

    I have to say I chose behaw because I wanted a more heavily modded experience here. I really don’t mind them shadow banning whole communities if a disproportionate number of trolls are coming over from them. People have got the right to speak, not the right to be heard. The internet’s full of kids just wanting to be obnoxious, and I’ve got to say I’m more then happy that other humans are helping me to filter that junk out

    • Cipher@beehaw.orgOPEnglish
      17·
      2 years ago

      When a Lemmy.World user posts to a Beehaw community right now, it updates the cached community that Lemmy.World stores. Beehaw has defederated with them, so the “source of truth” never updates. The source of truth is what updates other federated instances. As a result, someone on startrek.website, for example, will not see posts made by lemmy.world users to beehaw communities. The only people who can see what lemmy.world users post to beehaw right now are other lemmy.world users.

      • maynarkh@feddit.nlEnglish
        5·
        2 years ago

        Won’t that cause a major problem if/when Beehaw would want to refederate, and all that pent up stuff just pours on Beehaw all at once?

        • Cipher@beehaw.orgOPEnglish
          8·
          2 years ago

          When/if refederation happens, the comments lost to the abyss will stay lost to the abyss. The source of truth will not update based on the past updates of a formerly defederated instance to my understanding

        • Danar@discuss.tchncs.deEnglish
          2·
          2 years ago

          As far as I understand it (though it may be incorrect) - they won’t be synchronized. Content between instances is synced/cached only when the instances are federated, and it doesn’t go backwards - only posts after federation will be visible.

    • rknuu@beehaw.orgEnglish
      13·
      2 years ago

      Unfortunately, defederating means the cord has been cut. This means we still have what was previously been posted, but all future content is bidirectionally blocked.