@Yatin 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.
> Url in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 12-23: nzisd.co.nz Potentially bad keyword in title - Position 12-23: nzisd.co.nz Potentially bad keyword in username - Position 12-23: nzisd.co.nz Url in title - Position 0-23: https://www.nzisd.co.nz
> Numbers-only title, phone number detected in body, phone number detected in title ---------- Numbers-only title - Position 0-16: 1 (800) 674-9312 Phone number detected in body - Position 0-16: 1 (800) 674-9312 Phone number detected in title - Phone number: 1 800 6749312
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 1-18: gorecovermail.com Potentially bad keyword in title - Position 1-18: gorecovermail.com Potentially bad keyword in username - Position 1-18: gorecovermail.com
@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 title, pattern-matching product name in body, potentially bad keyword in body (292): Ten Acres CBD Oil by EvieRuther on apple.SE
@cigien Nope, no good reason, other than lack of diligence on my part. I just copy and pasted the title and didn't look at the URLs. Feel free to unwatch and add them. Thanks.
@Yatin Google translate suggests it's just innocent data. It's not spam, but I think TP is reasonable; IIUC this is something that could and should be blocked at the system level. Not sure though.
@tripleee Yeah, I agree. Just thought I'd mention it, since if the TP slow down, we might want to go back to just watching it.
@Yatin Same issue here. As far as I can tell, the link is broken. In general, if the report is more than a couple of years old, there's a decent chance that the link is broken. Spam tends to move around fast that way. Slippery stuff, spam ;)
@Yatin Thanks. While you could do that for very recent posts as well, they're always spam (in my limited experience at least), and can be watched without checking the link. One should still look out for FP of course, but that's much more important for blacklisting than just watching anyway.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, pattern-matching website in body, potentially bad asn for hostname in body, +2 more (361): Dubai Escorts services by Tamil Actress on stackoverflow.com
@Yatin That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
