Regarding Beehaw defederating from lemmy.world and sh.itjust.works, this post goes into detail on the why and the philosophy behind that decision. Additionally, there is an update specific to sh.itjust.works here.

For now, let’s talk about what federation is and what defederation means for members of Beehaw or the above two communities interacting with each other, as well as the broader fediverse.

Federation is not something new on the internet. Most users use federated services every day (for instance, the url used to access instances uses a federated service known as DNS, and email is another system that functions through federation.) Just like those services, you elect to use a service provider that allows you to communicate with the rest of the world. That service provider is your window to work with others.

When you federate, you mutually agree to share your content. This means that posting something to a site can be seen by another and all comments are shared. Even users from other sites can post to your site.

Now when you defederate, this results in content to be no longer shared. It didn’t reverse any previous sharing or posts, it just stops the information from flowing with the selected instance. This only impacts the site’s that are called out.

What this means to you is when a user within one instance (e.g. Beehaw) that’s chosen to defederate with another (e.g. lemmy.world), they can no longer interact with content on another instance, and vice versa. Other instances can still see the content of both servers as though nothing has happened.

  • A user is not limited to how many instances they can join (technically at least - some instance have more stringent requirements for joining than others do)
  • A user can interact with Lemmy content without being a user of any Lemmy instance - e.g. Mastodon (UI for doing so is limited, but it is still possible.)

Considering the above, it is important to understand just how much autonomy we, as users have. For example, as the larger instances are flooded with users and their respective admins and mods try to keep up, many, smaller instances not only thrive, but emerge, regularly (and even single user instances - I have one for just myself!) The act of defederation does not serve to lock individual users out of anything as there are multiple avenues to constantly maintain access to, if you want it, the entirety of the unfiltered fediverse.

On that last point, another consideration at the individual level is - what do you want out of Lemmy? Do you want to find and connect with like-minded people, share information, and connect at a social and community level? Do you want to casually browse content and not really interact with anyone? These questions and the questions that they lead to are critical. There is no direct benefit to being on the biggest instance. In fact, as we all deal with this mass influx, figure out what that means for our own instances and interactions with others, I would argue that a smaller instance is actually much better suited for those who just want to casually browse everything.

Lastly, and tangential, another concern I have seen related to this conversation is people feeling afraid of being locked out of the content and conversation from the “main” communities around big topics starting to form across the Lemmiverse (think memes, gaming, tech, politics, news, etc.) Over time, certain communities will certainly become a default for some people just given the community size (there will always be a biggest or most active - it’s just a numbers game.) This, again though, all comes down to personal preference and what each individual is looking to get from their Lemmy experience. While there may, eventually, be a “main” sub for <topic xyz> (again, by the numbers), there will also always be quite a few other options for targeted discussions on <topic xyz>, within different communities, on different instances, each with their own culture and vibe. This can certainly feel overwhelming and daunting (and at the moment, honestly it is.) Reddit and other non-federated platforms provided the illusion of choice, but this is what actual choice looks and feels like.

[edit: grammar and spelling]

  • @Ganbat
    link
    61 year ago

    I understand your why, but in the end, I think defederation is probably going to do more harm than good. Lemmy.world and beehaw are both large instances, and for a whole group on one, a non-negligible amount of content just disappeared. Sure, they could just make new accounts somewhere else, but there’s no way all of them will. For those that won’t, the whole of Lemmy just got a lot less valuable.

    I think that ultimately, large amounts of defederation, or just large instances defederation each other, is going to harm Lemmy and the fediverse as a whole. More people might migrate to smaller instances. Some will collapse under the strain, some might become big, follow the cycle and sew more division within the fediverse. A lot of people will get tired of juggling accounts and return to more toxic, but easier, centralized alternatives.

    Of course, just not defederating anything isn’t a solution either. Well, I mean, it is in a technical sense, but it doesn’t get to the root of the issue. My best idea would be some solution that allows users of certain instances to still see content and subscribe to communities, but limit their ability to interact. Think something like sliding defederation. Admins would be able to set what users of specific instances can and can’t do, from voting, commenting, submitting down to total defederation for the most extreme cases.

    Of course, the best code I’ve managed myself is a semi-functional python module, so…

    • @[email protected]OP
      link
      fedilink
      61 year ago

      The sliding scale is a really interesting idea that would strike a nice balance. Even something as simple (conceptually, probably quite the opposite infra and code wise) would be allowing an opt-in at the user level to see “unfiltered, unmoderated content from defederated instances”, similar to opting into nsfw content.