this post was submitted on 15 Jun 2023
615 points (100.0% liked)

Beehaw Support

2797 readers
31 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.


if you can see this, it's up  

founded 2 years ago
MODERATORS
 

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
[–] satouru@beehaw.org 9 points 1 year ago (3 children)

Aww, that’s a bit sad, but it’s completely understandable and probably the right decision as things stand. :(

Admins, to clarify, which “federation logic/tools” would you need to re-federate with those public/general-purpose instances? Maybe something like:

  • Beehaw users may read and write content on restricted instances,
  • Users from restricted instances cannot read or write content on Beehaw,
  • Unless the user from another instance is manually verified on Beehaw… maybe? But that would be much more complex in terms of development.

Would that be an acceptable solution? If so, I can try to get a look at Lemmy’s code and see if I can implement something like that - although no promises, as I’m currently completely unfamiliar with what lies under the hood of both Lemmy and the Fediverse.

(Not sure who to ping… @alyaza, maybe?)

[–] alyaza@beehaw.org 6 points 1 year ago

tools like this would be very ideal for this so we don't need to drop and/or maintain the defederation nuke, yeah. i'm not sure how exactly they'd be gone about, but to me at least they seem like the easiest way to make cases like this not end in a defed

[–] Gaywallet@beehaw.org 5 points 1 year ago* (last edited 1 year ago)

Bare minimum being able to stop users from select instances from posting or commenting. With that alone we can refederate.

I would personally like to see the ability to whitelist some of these users in some fashion. Applying to be able to post and comment, would be one method (probably the most complex but most desirable). Requiring that user accounts be a certain age, such as at least 30 days, or have a certain amount of activity like 30 posts or comments, might be a decent stop gap or a solution that lasts longer term - it's hard to know for certain because it partially depends on how many bad actors are drawn to the fediverse.

[–] mobyduck648@beehaw.org 2 points 1 year ago

I wouldn’t mind getting involved too if I have enough time in the next couple of months. Maybe there could be a beehawdev community on here or something?