This is my personal opinion, it is not the collective opinion of all lemmy.ml admins nor the broader Lemmy network as a whole. But I feel like no one is talking about this side of things, hence this post.

It seems that a major point of friction lately has been the registration screening questions that most large instances have, and the fact that instances which do not are being blocked. People are complaining about not knowing when they will be allowed to use their new accounts, if they will at all, as well as their instance being blocked by larger instances. While I empathize with the frustration this is causing, and I do agree that the registration screening system is far from perfect, I really feel the need to defend my fellow instance admins here, on all the major instances, and defend their decision to have registration screening.

We are all unpaid volunteers, and are running and/or moderating Lemmy instances because we are interested in doing so. In fact we have regular jobs and responsibilities that we juggle with moderating Lemmy. At the same time, we want to provide high quality spaces where users can interact and engage in meaningful discussion, and that requires that the threads be mostly free of trolls, abusive users, and spam. We have no automoderator, no automated content screening or spam/abuse detection in general, nor do we generally have enough people to even cover all 24 hours of the day (especially since instances tend to be run by people in the same or similar time zone). Registration screening goes a long, long way toward easing our workload and actually allowing our instances to function without getting overrun by undesirable content.

Lemmy, especially the larger instances, has been the target of many raids and brigades from places like 4chan. They were, I kid you not and you can find plenty of discussion about this if you go far back enough, posting anything from Nazi/fascist propaganda, to scat and gore porn, and rendered instances completely unusable for a time. Based on my experiences with lemmy.ml getting brigaded, enabling registration screening brought the number of abuse posts from tens or well over a hundred per hour to almost none, because just having to put that bit of work in to make a troll account is enough to discourage most people who have no interest in actually participating meaningfully, and it also makes it much more difficult to create multiple accounts for ban evasion, or to automate the creation of accounts in the form of a bot.

Also based on my own experiences, I can tell you that any instance with open registration is very quickly overrun by spam and abuse posts, to the point where it can make other, larger instances unusable if that influx of content is federated over, as well as generally massively increasing the workload of the admins on the other instances as now they have to pick up the slack and moderate what content from the open instance is actually real content that is allowed on their own instances. This would be happening in a time where those instance admins are already being swamped with new registrations and moderating the huge influx of content being generated from their own instance. Until a Lemmy instance gets large enough to actually hire full time admins to catch and remove abusive content ASAP, and/or implements reasonably accurate spam and abuse content screening that is resistant to evasion tactics, I don’t see instances reasonably being able to go without registration screening because the trolls will seize on that opportunity every time.

Admins of larger instances see it all the time:

  1. New instance pops up, yay! And most instances automatically federate with new instances!

  2. It doesn’t have registration screening, this is quickly discovered by trolls and adbots and the instance gets filled with rule breaking content.

  3. Large instances start blocking it because by federating with an instance that is being used in this way degrades the quality of your own instance and adds a ton of workload to your (unpaid) mods and admins. They specifically do this because they know that posting in small, brand new instances will also get their content forwarded to the large instances, because they have a harder time directly posting abuse on the larger instances. (We don’t block instances because “how dare they not have registration screening?!” We only really block instances when we start getting flooded with reports from our own users flagging the incoming abuse posts.)

  4. The instance eventually enables registration screening, and other instances start unblocking it.

  5. Repeat with the next new instance that pops up.

It’s happened with plenty of instances before and will probably keep happening as long as spam and trolling exist.

Most instances’ registration questions are fairly simple, and all we really want is for you to spend a minute of your time to write a few sentences, maybe a paragraph at most. You doing that reduces the workload for us, as well as contribute to a nicer environment for you and your fellow users.

  • BOB_DROP_TABLES@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Sounds very reasonable. Thanks for the post. I personally didn’t think it was a big deal when registering, just slightly odd. Didn’t give it much thought though. Unfortunately bots and trolls are constant problems to any online community. As Lenny grows, automated tools for moderation and spam prevention will likely be needed to help easy the work on the mods

  • Ulu-Mulu-no-die@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I don’t understand why some people make it such a big deal, it’s just a few minutes answering questions and it’s also much better IMO than traditional captcha that bots can solve.

    Noone will die for waiting a bit for the confirmation email and if it helps keeping instances clean it’s a very welcome system.

    I’ve seen some people having problems with receiving the acceptance email, that can be indeed confusing, but as I understand it, it was a bug that’s been already fixed, is that right?