@Yatin It means that MS went through your (and everyone's) flagging conditions and disabled any which were less than 99.75% accurate based on historical data. It also checks all of your flagging conditions together and verifies that all of them applied at the same time results in >=99.75% accuracy. If your flagging conditions in total (i.e. if you had more than one active flagging condition) resulted in <99.75% accuracy, then MS will have disabled all of them.
@RyanM 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.
@Yatin From the point of view of someone on the receiving end of such a message, you probably will want to go to metasmoke and edit your flagging conditions to adjust them such that they are >=99.75% and re-enable them.
@RyanM 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.
@SmokeDetector By Charcoal standards, the promotional bit at the end of this post is completely irrelevant self-promotion. I'm not flagging this because a site mod has commented to the effect that they have followed the disclosure rules, but I disagree that this content is not spammy.
Thank you for following the rules and making clear your connection to the site. — Ben I. ♦Nov 2 at 17:31
[ SmokeDetector | MS ] Blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in username, potentially problematic ns configuration in answer, +1 more (168): Add to Home Screen without creating PWA by karenminton on apple.SE
Half-baked idea: a rough estimate suggests that 17039 of our 25091 keyword watches are on literal domain names (specifically, they match \t([A-z0-9\-]+\\\.)+[A-z\-]+$). I wonder if splitting those out would buy us 1) a rule that could be non-experimental 2) files that are under the GitHub display limit 3) better performance due to not needed to run a regex engine on it (though regex engines might just be faster than Python due to ...well, not needing to execute any Python)
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, pattern-matching website in body, pattern-matching website in title, +3 more (487): skincreamfarm.com/boomin-keto/ by SalliZulia on apple.SE
And also nuke the whole account, and ban it for 1 year.
I've asked... And suggested it... But I've also been absent for ~6 months, so maybe the landscape changed.
Aside from actually sitting down to write the code, the tricky thing is the race condition. You have to wait long enough after reporting it before nuking that that MS has a chance to catch up.
Generally, we do request that moderators report spam, if it wasn't detected by SD. In fact, I was a bit quick on the draw on that one, so had to undelete it in order to report it. :;
I'm not a moderator, so I can't say what the best approach is. But I think if poke one of the other regulars here that is a moderator, I'm sure they're willing to help a colleague out.
Well, gotta be careful. If you ask a non-SO mod, they might not understand why I don't want to double (or more) the number of clicks it takes to nuke spam.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, potentially bad keyword in body (391): What is the use of OneShot Keto? by shotktoveu on meta.SE
@Mast Rules for Blacklisting and Watching. In case anyone asks again. Such links are a few clicks away from the [SmokeDetector] link that's frequently seen. --- That can be watched but might be purged if it's not reoccurring.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, blacklisted website in body, potentially bad ip for hostname in body, +1 more (363): Website Designing company in Delhi NCR by saya buzz on magento.SE
[ SmokeDetector | MS ] Url in title, bad ip for hostname in body, bad ip for hostname in title, bad keyword in body, bad keyword in title, +3 more (686): jdailytalk.com/aktiv-keto/ by RayanJohns on apple.SE
