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.

Avatar
TheDude@sh.itjust.worksM
68 points
*

Hey everyone, woke up this morning with this news. This news really comes at a surprise as I have not seen or heard of any trolling coming from members of this community. I also have not been approached by their admins to see how we could collaborate. In either case, I’ll be attempting to reach out to their admins and discuss a path forward together.

I’ll post an update with the details in the coming days.

permalink
report
reply
17 points

Their announcement doesn’t strike me as all that alarming. I could be mistaken.

It sounds like their mods have watched an unexpected expressway arrive at their door this week, Douglas Adams-style, and so they’re closing the door momentarily to evaluate what the new traffic will look like. Honestly feels reasonable, unless I’m misunderstanding it.

The message seems to be that this isn’t meant to be a permanent change.

permalink
report
parent
reply
7 points

That’s disappointing, I would’ve hoped that if open signups were their main problem then they would have communicated that. Other instances have “closed signups” but are effectively only bot gateways.

permalink
report
parent
reply
7 points

I really hope you find a way to re-federate. But they do have a point, open sign up is a a time bomb. Do you have any anti spam in place?

permalink
report
parent
reply
4 points

Ya maybe just approving sign ups is required during this wave. I dunno.

permalink
report
parent
reply
6 points

The more I read about beehaw, the more it seems like the admins are the kinds of people who would rather block everything they don’t like than look for an actual solution.

permalink
report
parent
reply
2 points
Deleted by creator
permalink
report
parent
reply
3 points

Elbows too pointy. Blocked.

permalink
report
parent
reply
-1 points

I had to block a user from this instance who posted something along the lines of “would you hit it” of three women wearing Nazi armbands. That made me nervous of this instance. It looks like Beehaw is seeing more behavior like that from this instance.

permalink
report
parent
reply
8 points

Report them. We’ll sort them out.

permalink
report
parent
reply
-2 points

I tried to find them again but I blocked them out of instinct and couldn’t get back to it. I find Nazi imagery particularly distressing, so I acted out of instinct instead of approaching it rationally.

permalink
report
parent
reply
85 points

Guys, can we please try to not act so butthurt about this? Simply accept that they were getting spammed and trolled and had to go private for awhile. It’s nothing personally against us or our community.

permalink
report
reply
16 points

This. We don’t know what kind of content was happening. It’s good that they’re trying to cultivate their communities along what they believe to be a good and positive ethos, and it’s even better that the Fediverse can support this without crippling everything.

permalink
report
parent
reply
6 points
*

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.

permalink
report
parent
reply
9 points

Isn’t that just a website?

permalink
report
parent
reply
7 points

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

permalink
report
parent
reply
9 points
*

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.

permalink
report
parent
reply
0 points

But they can ban those users, just like they get banned individually in their own communities.

There is pretty much no difference, unless organised brigading was going on from lemmy.world ,etc. which I doubt.

permalink
report
parent
reply
18 points

I’m not sure why you doubt it. People have corroborated that slurs were being mass spammed. I myself witnessed a troll on lemmy.world yesterday who dropped an f-bomb and told a lascivious tale about dessalines. They can ban them for 5 minutes until they make another account and start spamming again. It’s pretty easy for a handful of trolls to cause chaos, especially if they had only 4 mods. The mods need to sleep sometimes also.

permalink
report
parent
reply
7 points

Yeah, I saw a spammer on lemmy.world spamming scat porn images (unfortunately there is still no way of blocking all images). I reported them and they were banned.

They can ban them for 5 minutes until they make another account and start spamming again

But they can still do this from any federated instance. Meanwhile they just banned 20k+ contributing users.

permalink
report
parent
reply
4 points

Doesn’t have to be organized when there’s 30,000 people on the sites they’re blocking. It can be a marginal percentage of users and still be hundreds of people they need to ban. Potentially repeatedly if the banned trolls just start using sockpuppets.

A small number of mods + dedicated bad actors = blocking the tools those bad actors use.

permalink
report
parent
reply
36 points

I doubt this instance is being used by enough people to get trolls using it. It’s just because of the registration policy, which is open as opposed to the rest of the instances.

They just are too lazy to moderate it. Nothing to do with actual illegal content or imaginary trolls.

permalink
report
reply
24 points

It seems to me like they don’t want to give up any control by adding mods (currently it’s only the admins) and choose the easy way out by reducing the amount they have to moderate…

permalink
report
parent
reply
17 points

I think this is actually totally reasonable on their part. It does, however, mean that we need to start rebuilding some of the biggest communities elsewhere.

permalink
report
parent
reply
-1 points

Mods on their instance can’t moderate content sent from a community on i.e. sh.itjust.works.

permalink
report
parent
reply
22 points

Sure they can, they can ban the user from the entire instance or from the community. To all users of sh.itjust.works for example the content will still appear, but it won’t show on beehaw anymore.

Here’s the PR that implemented this: https://github.com/LemmyNet/lemmy/issues/1298

permalink
report
parent
reply
11 points

Yea if they want to defederate will all instances that have an open registration policy they are going to miss out on a lot of things, they are also going to have to defederate a lot of instances. I’m a little sad because theres a lot of decent content on that instance and is going to be inaccessible to a lot of users now, but whatever, their admins made their choice.

permalink
report
parent
reply
4 points
*

By my understanding, and I’d love to be corrected if I’m wrong, but we should be able to still see and interact with their instance their users just cannot see it

I’m a bit doubtful of this so I’ll have to check though

Edit: I am wrong

permalink
report
parent
reply
5 points

Unfortunately I don’t think we can. I’m still subscribed to News@beehaw and the last post showing up when viewing the community from sh.itjust.works is from 15h ago, while viewing it from beehaw.org shows there are many more recent posts.

permalink
report
parent
reply
4 points

Not really, the block goes both ways (they can’t see our content and we can’t see theirs) so effectively there are two communities for already subscribed communities

permalink
report
parent
reply
2 points

I hope this is the case, I would still like to be able to see their content, even if they can’t see ours.

permalink
report
parent
reply
34 points

I find this very disappointing, not because I’m hugely attached to Beehaw (although their large gaming community has dominated my feed this week). But rather because the first response to whatever adversity they were facing, real or perceived, is to take the nuclear option. The biggest drawback to Lemmy as opposed to Reddit is the over fragmentation and the lack of quality content, so intentionally increasing those challenges feels short-sighted and bad for the ecosystem as a whole.

permalink
report
reply
15 points

I would say that on lemmy mod tools are in pre-alpha state that work for instances under 1000 users. Lemmy needs more tools to moderate and without any other option beehaw decided to go nuclear until they get mod tools

Whole reddit debacle was about 3 party apps and moderation tools

permalink
report
parent
reply
15 points

Ok so help me understand here. The root post is Beehaw complaining that their four admins can’t handle the new influx of users. But isn’t that the entire point of moderators? Shouldn’t each community be responsible for dealing with trolls, etc? From what I’ve seen of Beehaw, they’re attempting to have the same handful of admins moderate every single community, which was never going to be sustainable and IMHO misses the entire point of this sort of experience.

permalink
report
parent
reply
16 points

If all the new trolls are coming from two instances, and defederating those two instances will keep the load manageable for them, why wouldn’t they?

This kind of decision is a big problem for scaling up Lemmy as a reddit replacement and welcoming huge volumes of new users, but I don’t think that’s Beehaw’s goal and certainly not their responsibility.

The tricky bit is figuring out how to set up fediverse-wide communities in places that most (non-troll) users won’t be cut off from them.

permalink
report
parent
reply
6 points

I don’t know how to answer the question. I don’t have enough information but from my testing moderation tools are in a poor state and what moderator can do if they can’t moderate.

permalink
report
parent
reply
15 points

I tend to agree. Their server, their rules, but an attempt to find a compromise of some variety rather than suddenly and unexpectedly defederating would have been nice.

permalink
report
parent
reply
26 points
*

This sort of stuff was always gonna happen early on. As things calm and the wider community settles into some norms we’ll see less of it.

permalink
report
reply

sh.itjust.works Main Community

!main@sh.itjust.works

Create post

Home of the sh.itjust.works instance.

Community stats

  • 259

    Monthly active users

  • 427

    Posts

  • 11K

    Comments