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?

  • trachemys@iusearchlinux.fyi
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 year ago

    Two separate issues are prompting “defederation”. Blocking users from posting to your local community and blocking remote communities from being mirrored on your server. Those should be handled differently. Beehaw didn’t want trolls posting mean things and blocked every user on a server. Your concern about illegal content would be more a complaint about specific communities that feature that content.

    Either way you shouldn’t blame an entire server for a few users or communities you don’t want. Expecting everyone on a instance to be like minded isn’t going to work.

    • Cipher@beehaw.orgOP
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      The only way to not address things on a per-server basis is for moderation tools to be expanded in scope. Maybe that will be how things work one day, but it is not how things can work right now.

    • RoboRay@kbin.social
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      If that’s the only way to stop harassment, yes, you do… anyone on that instance that isn’t like-minded with the behavior that instance permits is well-advised to leave it for one better suited to their own beliefs.

        • RoboRay@kbin.social
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          1 year ago

          I’m not opposed to any process on any instance that enforces civil behavior on its registered users. Moderation is mandatory to eliminate defederation as the only way to handle the problem.

          If you refuse to moderate your instance, you forfeit any right to complain about your instance getting defederated.

          But these things are still too young and primitive for good moderation tools to exist yet… yet.

    • polaroid@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      It’s a stopgap measure until better moderating tools are developed. I can’t blame them for it.