I just want to know if reports are failing for anyone else and if we need to be making some kind of plea to the admins/moderation teams/developers to try to fix it.
Because not being able to report this obvious spam is a problem.
I just want to know if reports are failing for anyone else and if we need to be making some kind of plea to the admins/moderation teams/developers to try to fix it.
Because not being able to report this obvious spam is a problem.
I’m assuming the issue is the new nicole has already been banned by the time you are responding to it, thus there’s nothing new to report.
Far as solutions, only ones I can imagine are I guess to allow instance owners to auto block and ban messages featuring certain words/sentences, and maybe auto delete messages from already banned users, in terms of technical solutions to getting ahead of the whack a mole game.
Some admins have been developing and sharing solutions, from regex filters to going down into the databases itself.
For my small instance and personally, I haven’t seen any new messages in a while now, after adding this regex to the slur filter mechanism:
(.*(\n)*Hi.*[nN]icole.*[fF]ediverse [cC]hick(.|\n)*)Sadly my brain is blanking which instance admins I should credit for that, but it was shared around somewhere.
Ha, I literally just got a new message with spaces between every letter to try to get around filters like this.
Makes sense, it’s most likely an ongoing arms race - I’m probably coasting under the radar a bit from running an instance with effectively only 3 people to target at the moment.
I love how useful Regex is. I hate writing Regex. Special shout out to anyone who can do it well.
Regex is great, but PCRE deserves a special place in hell. You don’t know unreadable until you’ve encountered regex that uses recursive matching, backrefererences, and subroutine calls.