107
ANNOUNCEMENT: defederating effective immediately from lemmy.world and sh.itjust.works - Beehaw
beehaw.orghey 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
[https://beehaw.org/post/520044?scrollToComments=true] 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. 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.
Interesting bit of news for the threadiverse. All three of these are fairly large lemmy instances
The admins have always been clear that they’re not trying to replace Reddit, and I’m quite sure they were not trying to be one of the largest instances.
If they weren’t trying to get large then how did that happen? Based on admin comments, beehaw was one of the more active instances when the first wave of migration happened; and a decent amount of the pre-first wave posts about lemmy I saw on Reddit were about how Beehaw was a good instance to join as it was defederated from lemmygrad.
I’m not saying this has anything to do with replacing reddit but it is bad for the larger threadiverse community. Notably there were several other instances that closed registration for the purposes of not growing quicker than they could handle long term (see lemmy.ml). Beehaw has most of the largest (and therefore defacto default) communities. Active steps to avoid that would have allowed them to maintain their moderation goals while growing in an organic and sustainable way that benefits the larger threadiverse community.
I was strictly replying to the part of your comment where you said they made a decision to try to be one of the largest instances – imo they did not make a explicit decision to try to be that, but rather the growth was a side effect of the circumstances around reddit users checking out the fediverse.
Is closing registrations is better than having an application with questions that weed out low-effort users? IMO it’s probably a wash. beehaw has only banned one user from the local instance that I know of, so the application process seems to be working overall. The issue is that other instances are growing too quickly and needing to moderate those users, not their own.
I do agree this isn’t great for the threadiverse and I wish it hadn’t come to this, both on a personal and community level. I was subbed to the knitting community on lemmy.world, it was the most active of those communities that I saw, and now I’m locked out. Idk if I want to move to an alt on a different instance, or self-host my own so that I’m fully in control of what I can see, or what. :S
No the issue is that four moderators for the whole instance was always unsustainable and allowing the communities to become the defacto defaults without growing the mod teams was a bad idea. This was easily foreseen and corrected. Blaming other instances is not at all fair.
you do not understand the problem. The growth was on every server of the fedivers - so moderationg users from different servers was to much work. how should they stop people from other servers? two options - block any individuell(which is to much work with so many open registration servers - they can just spamm new servers) or nuke the server where most of the trolls come from.
I DO understand the problem. They only have an issue with an influx of users because they are the largest (defacto default) communities. A position that was incompatible with their moderation system from the get go. Had they had more sustainably sized communities none of this would have been an issue.
The moderated, reasonable stance is that everyone is right! Beehaw probably could have done things differently, including making a stickied post that they don’t want to be the default large instance, and/or acquired a lot more mods to manage the federation of other large instances. On the other hand, Lemmy doesn’t have the same principles as Beehaw and prioritized the growth of their userbase over a filtering system. To you it looks like one is worse than the other, that’s because you want to see content from everywhere and don’t share the principles of the other federation - so you’re probably not a good fit for Beehaw atm (and if anyone is blindsided, I don’t get it… I could see it written all over Beehaw that they are trying to promote certain principles over growth, I don’t share in those principles but I can respect that they were direct about it).
Everyone on the Fediverse should expect to see instances un/re-federate several times over especially in the growing stages. The critique is fine but it should definitely be tempered with reasonable expectations and not unnecessary ridicule.
The idea that people are missing content on Lemmy/Beehaw/Kbin instances that get defederated are looking at this from a “this should be super convenient” mentality which, convenience is why Reddit expects you’ll go back. Quality of content, genuine community-building, and/or responsible upper management doesn’t have as much value there, it is inherent in them being a VC, convenience is what matters most on Reddit/TikTok/Twitter/etc.
On the Fediverse, the one thing that should be said more is that the instance you join, you should prepare to be involved locally through that instance more than anything else. The idea you can or should just join anywhere was something I wrong wrong about, as was much of the Reddit people saying “join Lemmy it doesn’t matter where, it’s all federated.” I don’t blame them or myself, it’s a newer concept and nuance is lost at the entry- level to anything. If people were coming to the Fediverse for fully federated, more convenient content than they should try Mastadon, because they’re farther along and had their own issues to deal with during the Twitter migration that propelled them much like these instances that are still growing and learning will, in time.
That’s not necessarily true. There’s both approaches at work here, one is the “themed community” one, and the other is the “universal citizen” one. That user/forum migration has not been implemented from the beginning (but it will hopefully asap), speaks rather more about the mindset of the developers. I myself would find it an absolute no-go if i would be participating in the technical desigh of a social server network, if servers were to own users and communities. That would lead to the exact same problems as corporate sites pose – they are governed by people with specific mindsets, and that is to be avoided.
There are 4 admins and 30-something mods.