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?

  • flatbield@beehaw.orgEnglish
    9·
    2 years ago

    I do not think that anyone “likes” de-federation. In the end though people coming in from other nodes are guests in our forums. We do not have to put up with bad behavior. Moreover instances that allow their users to engage in this bad behavior take some responsibility too. They are your users after all. So if your instance gets banned look to your instances users, and also the admins and their policies that allow those users on that node. Do not under estimate the troll problem. Moderation is required and if it cannot be done effectively then other actions have to be taken like de-federation.

    Then again, your coming from lemmy.ml and are not de-federated so why do you care. It is also a bit rich when lemmy.ml has not accepting subscriptions from behaw since I joined. Maybe you should complain about that too.

    • Grogula@feddit.nlEnglish
      2·
      2 years ago

      Then again, your coming from lemmy.ml and are not de-federated so why do you care.

      This is a terrible argument, in any case.

      • flatbield@beehaw.orgEnglish
        2·
        2 years ago

        Maybe a better one is that lemmy.ml has not been accepting subscriptions for some time. It also has it’s own block list in terms of federation: https://lemmy.ml/instances too. Most instances will not federate with everyone and will block some to protect their communities. It is just a fact.

        As I said, I do not think it is a desirable thing in general and it is disruptive when transitioning to blocked but it is from time to time necessary. The necessity has to be jugged from the point of view of the instance making the decision and their admins. So projecting some other set of concerns onto it is kind of questionable. It is even more questionable when your instance is doing similar things and worse when users from your instance were the ones causing the issue to start with.