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.
Boost refuses to mark their messages as read for some reason
It does that with any unread message for some reason. Going to your replies and then tapping the double check mark in the top right marks everything in the inbox as read, as well.
I should probably let the devs know about this bug… When I don’t forget.
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.
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.
