@Makyen I had assumed (and heard) that there would be some amount of duplicated effort when it comes to handling flags. I'll admit I wasn't expecting it to be frequent enough to be a daily occurrence. That is quite unfortunate, and I can definitely see that being demotivating.
@cigien That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@SmokeDetector tpu- undisclosed affiliation. Repeated offense (on different site) after being warned. Custom flagged on both with link to domain on MS indicating a longer history of spamming than just the last couple of posts.
[ SmokeDetector | MS ] Bad keyword in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially bad keyword in username (91): MySQL connection error on drupal system by Jeremy Zucker on serverfault.com
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (235): Have you done your marketing today? by 99 Digital Academy on english.SE
@double-beep That pattern looks like it's already caught by Blacklisted website in body, Blacklisted website in answer, Potentially bad keyword in answer, and Potentially bad keyword in body; append -force if you really want to do that.
@Spevacus That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
According to both FAQ, rollbacks invalidate spam/rude flags. To test this theory and have the accurate representation of what the system does, I flagged this answer as spam and proceeded to roll it back to the previous revision. I expected the flag to be dismissed, but it wasn't. I rolled it back...
I've been scouring the code trying to figure out how this works since you posted it and... I cannot actually find any references in the current code that would even attempt to clear Spam/Offensive flags on a rollback. It doesn't appear to be broken more than completely removed, and I have no idea why. — animuson ♦2 hours ago
@Spevacus That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@ThomasMarkov If you are privileged with Smoke Detector, you can type !!/report (link to question) to manually report a post.
You can also manually report it via the Metasmoke API, as double-beep did with that post, through the use of various userscripts (though these all require you to be privileged with SD as well)
