@SmokeDetector This intentionally abuses the system in order to try to bump the user's question. It uses non-visible characters in order to meet the length limit. It was their second such answer on the question. While I might consider something similar NAA under other circumstances, TP seems fine on this one. The user has been deleted or destroyed.
@ThomasWard You can upgrade that to a year+. sigh I did actually do more work on it within the last few/several days. It's high on my priority list for work. It's also gating work on a few things, so that makes it even more important. However, a couple/few issues directly pertaining first to the Thanksgiving MS outage, then the spam wave have resulted in me working on those things, mostly. I have spent some additional time on the Posts issue past that.
In other words, I'm still working on it, but need to clear a couple/few things first in response to ongoing issues.
unrelated: Geez the Bachelorette runs for two freaking hours? No wonder I hate the show. (it's eating up disk space on my parents' DVR though... and I know this 'cause I used my Dad's account to access it and watch the DVR'd stuff I care about xD)
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad keyword in answer, potentially bad keyword in username, username similar to website in answer (70): event planners services by Genu Venue on webapps.SE
@gparyani - Looking at the recent spam on German.SE (1, 2), I noticed this entry in MetaSmoke from 2018 which was treated as a TP (you were one of the users who gave feedback), but it seems that it's at best NAA (the linked site, duden.de, is for a legit German dictionary).
The user appears to not have other entries in MetaSmoke either, so it seems to not be a troll. Am I missing something here?
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, numbers-only title, potentially bad keyword in body (323): 142152156216216126126 ✏️ by aw1324 on ru.stackoverflow.com (@VictorVosMottor)
It should, but the commits for the blacklist didn't remove them because the number pattern I used wasn't identical to the one in the watched_numbers list. If it was it probably would've removed it (like what happened just a bit ago here)
