this post was submitted on 15 Jun 2023
106 points (97.3% liked)

sh.itjust.works Main Community

7735 readers
1 users here now

Home of the sh.itjust.works instance.

Matrix

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] imaqtpie@sh.itjust.works 84 points 1 year ago (3 children)

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.

[–] TheBeege@lemmy.world 16 points 1 year ago

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.

[–] Ferk@kbin.social 6 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[–] Antipaganda@kbin.social 9 points 1 year ago

Isn't that just a website?

[–] Kichae@kbin.social 7 points 1 year ago (1 children)

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

[–] Ferk@kbin.social 9 points 1 year ago* (last edited 1 year ago) (1 children)

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@sh.itjust.works 2 points 1 year 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.

[–] nivenkos@lemmy.world 0 points 1 year ago (2 children)

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.

[–] imaqtpie@sh.itjust.works 18 points 1 year ago (1 children)

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.

[–] nivenkos@lemmy.world 7 points 1 year ago (4 children)

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.

[–] Barbarian@sh.itjust.works 13 points 1 year ago* (last edited 1 year ago) (1 children)

It'll be interesting to see if they block kbin.social, fedia.io and startrek.website soon. All these same arguments work for them.

[–] exohuman@kbin.social 3 points 1 year ago (1 children)

When federation wasn’t working for kbin, the community felt like a safe space. It was calm and interesting. With federation in place the main negative thing I have seen so far is downvotes everywhere. Yes, the Lemmy community feels a lot more Wild West too than kbin did.

[–] Barbarian@sh.itjust.works 6 points 1 year ago (1 children)

I obviously can't talk for every single sh.itjust.works user, but it doesn't feel like that here to me, even with federation on. It really depends on the instance and the subscriber base.

[–] imaqtpie@sh.itjust.works 4 points 1 year ago (1 children)

Barbarian, you're a gentleman and scholar. Your patience and understanding of the fediverse has been crucial to the success and growth of this instance, and indeed Lemmy as a whole. So thankful you joined up with sh.itjust.works. Keep fighting the good fight!

[–] Barbarian@sh.itjust.works 2 points 1 year ago

I appreciate that, thank you.

[–] imaqtpie@sh.itjust.works 12 points 1 year ago (1 children)

They didn't ban us, they temporarily defederated from our instances. Totally different things.

And no, I don't think there are very many instances which are as quick and easy to make an account as us and lemmy.world. That's how we grew so quickly, and we obviously picked up a few trolls along the way.

[–] nivenkos@lemmy.world 10 points 1 year ago (2 children)

"temporarily"

It just reminds me of all the Mastodon drama, like them de-federating the Swedish one over not applying shared blocklists, etc.

Why not focus on blocking actual abusive users, and contributing to shared tooling, rather than trying to pre-emptively ban users?

[–] imaqtpie@sh.itjust.works 13 points 1 year ago (1 children)

You're not wrong. I just think you're choosing a silly hill to die on. What is the purpose of your line of questioning? Do you want to be federated with them or not?

Do you have any experience moderating a Lemmy instance of that size? Presumably they would have been focusing on blocking abusive users for the past week and ultimately decided they had to choose nuclear option.

Neither of us actually know firsthand what went down, but I'm choosing to sympathize and you're choosing to criticize. Neither of us is necessarily wrong, but I feel it's wiser to be supportive right now, given that we don't know what the future might hold and the platform is in a fragile state.

[–] nivenkos@lemmy.world 10 points 1 year ago (2 children)

The issue is that it affects the growth of Lemmy as a whole. Like the outcome of all the Mastodon drama was just that I gave up using it, but I was never a big Twitter use anyway.

Imagine the average Redditor's experience now - they come to browse some Lemmyverse posts. See that Beehaw has active Gaming and Technology communities like Reddit, so try to sign up there. Wait 2-3 hours with no response to their registration and then give up and go back to Reddit.

[–] imaqtpie@sh.itjust.works 11 points 1 year ago

Ok, I see where you're coming from.

I guess I just don't feel the same because I never expected the original servers to be anything but an afterthought. From my perspective, Beehaw was never going to play a large role in the growth of this platform. It was kinda obvious that they were going to have a problem with the influx of users. So getting this out of the way early is actually one of the best ways for it to play out

[–] FantasticFox@lemmy.world 13 points 1 year ago (2 children)

There is nothing more permanent than a temporary solution.

[–] Trebach@kbin.social 9 points 1 year ago

// This is meant to be a temporary solution

I found that in a SQL script from 2001...in 2018.

[–] aeternum@kbin.social 7 points 1 year ago

haha. I'm still rocking a temp solution I put in place on my media server about a year ago.

[–] JohnnyCanuck@sh.itjust.works 5 points 1 year ago (1 children)

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.

Isn't the issue that this instance (and some others) don't have any controls on creating new accounts?

[–] nivenkos@lemmy.world 4 points 1 year ago (1 children)

Neither does Reddit.

What is your proposed solution? Private invites like lobste.rs ? Or the current tiny trickle of allowed users on Beehaw ?

I think open growth and banning spammers while developing analysis tools to automate it is the best way.

[–] JohnnyCanuck@sh.itjust.works 0 points 1 year ago

I was just explaining what their issue was, I wasn't defending it or proposing any solutions.

[–] kukkurovaca@sh.itjust.works 4 points 1 year ago

They can do this from any instance with open registrations. Instances with closed or moderated registrations are a different story. So, could just as easily say, why doesn't sh.itjust.works restrict new user creation, which is a common practice on smaller fediverse instances including beehaw.

(Answer: then you can't onboard new users in a mass migration. But that's what creates the tension.)

[–] Kichae@kbin.social 4 points 1 year ago

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.