cross-posted from: https://beehaw.org/post/567170

We’ve been defederated. Were there that many trolls/assholes on our server? What on earth happened while I was asleep?

hey folks, we’ll be quick and to the point with this one:

we have made the decision to defederate from lemmy.world and sh.itjust.works. we recognize this is hugely inconvenient for a wide variety of reasons, but we think this is a decision we need to take immediately. the remainder of the post details our thoughts and decision-making on why this is necessary.

we have been concerned with how sustainable the explosion of new users on Lemmy is–particularly with federation in mind–basically since it began. i have already related how difficult dealing with the explosion has been just constrained to this instance for us four Admins, and increasingly we’re being confronted with external vectors we have to deal with that have further stressed our capabilities (elaborated on below).

an unfortunate reality we’ve also found is we just don’t have the tools or the time here to parse out all the good from all the bad. all we have is a nuke and some pretty rudimentary mod powers that don’t scale well. we have a list of improvements we’d like to see both on the moderation side of Lemmy and federation if at all possible–but we’re unanimous in the belief that we can’t wait on what we want to be developed here. separately, we want to do this now, while the band-aid can be ripped off with substantially less pain.

aside from/complementary to what’s mentioned above, our reason for defederating, by and large, boils down to:

  • these two instances’ open registration policy, which is extremely problematic for us given how federation works and how trivial it makes trolling, harassment, and other undesirable behavior;
  • the disproportionate number of moderator actions we take against users of these two instances, and the general amount of time we have to dedicate to bad actors on those two instances;
  • our need to preserve not only a moderated community but a vibe and general feeling this is actually a safe space for our users to participate in;
  • and the reality that fulfilling our ethos is simply not possible when we not only have to account for our own users but have to account for literally tens of thousands of new, completely unvetted users, some of whom explicitly see spaces like this as desirable to troll and disrupt and others of whom simply don’t care about what our instance stands for

as Gaywallet puts it, in our discussion of whether to do this:

There’s a lot of soft moderating that happens, where people step in to diffuse tense situations. But it’s not just that, there’s a vibe that comes along with it. Most people need a lot of trust and support to open up, and it’s really hard to trust and support who’s around you when there are bad actors. People shut themselves off in various ways when there’s more hostility around them. They’ll even shut themselves off when there’s fake nice behavior around. There’s a lot of nuance in modding a community like this and it’s not just where we take moderator actions- sometimes people need to step in to diffuse, to negotiate, to help people grow. This only works when everyone is on the same page about our ethos and right now we can’t even assess that for people who aren’t from our instance, so we’re walking a tightrope by trying to give everyone the benefit of the doubt. That isn’t sustainable forever and especially not in the face of massive growth on such a short timeframe.

Explicitly safe spaces in real life typically aren’t open to having strangers walk in off the street, even if they have a bouncer to throw problematic people out. A single negative interaction might require a lot of energy to undo.

and, to reiterate: we understand that a lot of people legitimately and fairly use these instances, and this is going to be painful while it’s in effect. but we hope you can understand why we’re doing this. our words, when we talk about building something better here, are not idle platitudes, and we are not out to build a space that grows at any cost. we want a better space, and we think this is necessary to do that right now. if you disagree we understand that, but we hope you can if nothing else come away with the understanding it was an informed decision.

this is also not a permanent judgement (or a moral one on the part of either community’s owner, i should add–we just have differing interests here and that’s fine). in the future as tools develop, cultures settle, attitudes and interest change, and the wave of newcomers settles down, we’ll reassess whether we feel capable of refederating with these communities.

thanks for using our site folks.

  • Ferk@kbin.social
    link
    fedilink
    arrow-up
    8
    arrow-down
    2
    ·
    edit-2
    2 years ago

    Personally I’d rather there were methods for people to access content across instances without the instances having to federate. So that the repercussions of defederation can be minimized. Then it would not be a big deal at all even if an instance didn’t federate with anyone else.

    I feel that it’s actually a big ask to expect the owners of an instance to host/proxy whatever content all other third party instances provide. If I was hosting my own instance I would actually rather prefer to not federate with anyone, because I would not want to be liable / responsible for hosting content that I don’t even have control over. Specially if the fediverse ever becomes as big and mainstream as massive social networks like reddit.

    • Kichae@kbin.social
      link
      fedilink
      arrow-up
      7
      ·
      2 years ago

      You can always access content on other instances, assuming they’re not private. Just enter the URL into your browser bar.

      • Ferk@kbin.social
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        2 years ago

        Yes, but then I’d need a whole new account to keep a list of subscriptions, and completely switch to a different website / feed.

        The interesting thing would be if the same frontend could make the requests to the the API from multiple instances directly (cross-site) to fetch subscriptions for each instance and aggregate the content in the same feed, even across instances that do not federate.

        Ideally you’d get the content from those instances without server-to-server communication, and you wouldn’t need instances to proxy/cache the content from each other’s. Each instance would just serve the content they host when they do not federate. So they wouldn’t be held responsible for 3rd party content while still giving you the freedom to chose to connect with those other instances if you really want.

        Of course it would still require some level of coordination for all instances to use the same standards, and be able to authenticate the user consistently (maybe using a cryptographic key). But I expect it would alleviate the inter-instance drama by removing friction.

        • kiboutrash
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 years ago

          I agree that it’s frustrating that we can’t still view content and just be unable to interact from our instance. That being said, I think a workaround to have everything in one place (if you just want to lurk) would be adding that specific community’s xml link to an RSS feed along with your sh.itjust.works homepage’s xml.