Actually I don't know how it works. Perhaps because it has been automatically reported, not manually reported...? - Automatic report: Looks like spam but not [manually] reported - Manual report: Post has already been reported
The pin for the prior one shouldn't have expired for another 1/2 hour, assuming it's pinned for an actual 15 days, rather than 15 days +/- N minutes. Other things on SE happen if they are within a band of time when the task to do them runs, rather than that the full time has expired (e.g. close votes expire in 3.5 to 4.5 days, not at 4 days, or only after 4 days), so maybe this is similar.
@Makyen It looks like the prior "Links" message is staying up for now. I'll re-post this if the old one drops off again and doesn't get re-pinned by someone else.
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body, blacklisted user (73): Https G Co Recover by john on webapps.SE
@tripleee Fair enough. Can I apply the same logic to keywords as well? I have a number of #drug keywords hovering around 4 TP. Is it ok to blacklist those as well?
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, potentially bad ns for domain in body, +2 more (393): What is Geehii Keto by AlisonSchult on apple.SE
@cigien Please don't. My opinion is that just the fact that something is drug related or fake tech support related does not make it a Preexisting Campaign.
@SurajRao Oh, I see. I don't think it was reported before. MS only shows one report for that post at least. Not sure why it wasn't caught before.
@Makyen That's reasonable. I'm not entirely convinced, but I'll stick to the current guidance strictly for now, until I have a strong argument against it. cc @tripleee Thanks for responding immediately BTW, I was going to blacklist half a dozen keywords in the next half hour otherwise.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body (292): Synopsis Prime EXT Review by user404682 on apple.SE
@tripleee 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.
