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?

  • Dav@kbin.social
    6·
    2 years ago

    Here’s an analogy, hope it helps:

    Kbin.social and beehaw.org are like really advanced email servers (e.g. outlook.com, gmail.com)
    The content you’re seeing on kbin is like viewing an email sent from another server, in the case of this thread you’re getting content from beehaw.org.
    These aren’t just normal emails, they’re super advanced emails with comments, replies, categories, votes etc.
    The content is downloaded to the kbin servers for your viewing pleasure, and you can send an ‘email’ back to beehaw by engaging in their posts/communities like you’re doing now. That will send what you’ve done back to beehaw so it’s all synced up for their users.

    If beehaw ever goes down/gets unlinked from kbin you’ll still have the old ‘emails’ (content) but you won’t be able to engage with them anymore. Like if someone deleted their email account it doesn’t delete all the emails they sent to other people.

    • floofloof@lemmy.ca
      1·
      2 years ago

      I’m new here and not up on the history, but I have a couple of questions:

      1. When an instance defederates, does it disconnect from all other instances? Or can the administrators choose which other instances they no longer want to sync up with?

      2. In the case of content remaining on my local instance that originated on another instance that has since defederated, would I be able to tell? Would it be possible for Lemmy to add a visual indicator that this content had become disconnected from its originating instance?

      • Dav@kbin.social
        1·
        2 years ago
        1. They can choose who to defederate, pretty sure beehaw has already done so with lemmy.ml and others.
        2. I think every instance is different but on some if you try to sub to a defederated community it’ll get stuck on ‘pending’, also you’ll probably see a lot of posts about it. It doesn’t seem to be something that’ll happen often.