[ SmokeDetector | MS ] Bad keyword in body, bad keyword with email in body, bad phone number in body, blacklisted username, pattern-matching email in body, +2 more (488): REVIEW FUNDS RECOVERY by bryan pulisic on security.SE
@Yatin I see, thanks. Yeah, that question was bound to get at least a couple of R/A flags as well as a bunch of downvotes. However, it looks like a completely legitimate question to me. It would probably make for an interesting discussion on cooking Meta. I'm going with FP.
@Yatin 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 | MS ] Bad keyword in body, bad keyword in link text in body, link at beginning of body, potentially bad ns for domain in body, potentially bad keyword in body (208): What is ISO Certification in Malaysia? by abdul wasim on askubuntu.com (@Ollie)
PR#6019 ("Yatin: Watch dheeraj@advaana\.com(?# not watching the usual way, dheeraj is a common indian name and will cause FPs on its own)") opened by SmokeDetector
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, Bad keyword in body, and Bad keyword in answer; append -force if you really want to do that.
For a while, we've had a certain "pluralization" sort-of-troll on Meta.SE, who occasionally but constantly reposts reports about pluralization bugs in the SE software, "demanding" that SE fix the bug and trolling against users who vote their posts as duplicates of existing reports.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, potentially bad keyword in body, potentially bad keyword in title, +2 more (397): lllllllllllllllllllllllll ✏️ by Muffin on stackoverflow.com
> Potentially bad keyword in title, scam aimed at customers in title ---------- Potentially bad keyword in title - 8886384491 found normalized Scam aimed at customers in title - Targeting *airlines* customers. Keywords: *phone, number*
@PeterJ To avoid SmokeDetector reporting posts too slowly, you can report at most 5 posts at a time. This is to avoid SmokeDetector's chat messages getting rate-limited too much, which would slow down reports.
