Odd watch match, error in bisect and/or anchoring logic? #6834
Labels
area: blacklists
area: commands
area: spamchecks
Detections or the process of testing posts. (No space in the label, is because of Hacktoberfest)
status: confirmed
Confirmed as something that needs working on.
type: feature request
Shinies.
What problem has occurred? What issues has it caused?
The post https://metasmoke.erwaysoftware.com/post/353825 was reported as a title match, but
!!/bisect
et al. don't reveal why.https://chat.stackexchange.com/transcript/message/60613689#60613689 shows several of us trying to figure out what caused it, but failing.
Eventually I hacked
findspam.py
to reveal which rule matched, and it came back with the watchlist after all. (Investigation still pending, though. This might still be a red herring.)What would you like to happen/not happen?
Several things really.
!!/bisect
might be best left as it is, though then we'd want to have a separate troubleshooting command for chasing down the match from various regexes insidefindspam.py
.!!/bisect
and the actual watch/blacklist logic, it needs to be found and corrected.Sorry for the messy ticket, I'll hopefully be able to clean this up somewhat later on.
The text was updated successfully, but these errors were encountered: