21
Your feedback is needed
(dataterm.digital)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jun 2023
21 points (100.0% liked)
DATATERM Main
5 readers
2 users here now
This is the main channel of DATATERM. Here you can post off-topic content if you want.
founded 2 years ago
MODERATORS
That won't stop the trolls, now they'll just create burners on beehaw itself. They are hurting innocents to do exactly nothing.
It won't stop them but it severely hinders them.
Beehaw's registration process takes time. Rather than spin up a bunch of accounts instantly and troll rapidly (causing massive admin/moderator overhead), they'll have to register direct with beehaw. This limits the number of accounts action has to be taken against.
Looking at it from an attackers perspective, is it worth it to wait 1+ days of going through a registration that requires the user submit answers to a questionnaire, just to troll users on beehaw? Probably not.
Until other instances defederate, your path of least resistance is to stay put. When that changes you'd reassess, and move elsewhere.
you'd create the burners en masse and then burn them one at a time.
I understand that. Beehaw has a questionnaire they require to be filled out as part of their application process.
You can filter verbatim responses (if 100 accounts have the exact same responses, they're probably not legit) and do other things to help cut down on bot accounts being used for trolling. This is why I said it's a severe hindrance, not a 100% perfect solution.
Additionally, they can just attach themselves to other instances anyways. It's impossible to stop them unless you make yourself an island and make it beyond hellish to sign up. Meanwhile you've affected the 99.9% of good people on that instance by cutting them off. It just doesn't make sense to me.