@cigien Something we could do is create a list of these exceptions on the Team. Some sort of canonical for the watch/blacklist. I wonder if that would be too big to be unsustainable.
@ppwater Oh, I didn't think of that. That doesn't sound like much of an issue, since spam flags would also kick it off the front page, but I'm not sure.
Wait, also, don't we want spam to not be visible? :p
@cigien 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 | MS ] Bad ip for hostname in body, body starts with title and ends in url, link at end of body, potentially bad ns for domain in body, potentially bad keyword in body (299): Men Booster Coffee by Fesin Worth on meta.SE
I would hope so, but I don't know. Apparently if you blacklist and watch similar things it breaks the CI. You have to unwatch if you want to blacklist or something. Again, not sure at all. I only understood about half that conversation :p
@ppwater That pattern looks like it's already caught by Bad keyword in body, Blacklisted website in answer, Bad keyword in answer, Blacklisted website in body, Potentially bad keyword in answer, and Potentially bad keyword in body; in addition, the regex contains an unescaped "."; in most cases, it should be "\."; append -force if you really want to do that.
:56550215 That pattern looks like it's already caught by Bad keyword in body, Blacklisted website in answer, Bad keyword in answer, Blacklisted website in body, Potentially bad keyword in answer, and Potentially bad keyword in body; in addition, the regex contains an unescaped "."; in most cases, it should be "\."; append -force if you really want to do that.
@ppwater That pattern looks like it's already caught by Bad keyword in body, Blacklisted website in answer, Bad keyword in answer, Blacklisted website in body, Potentially bad keyword in answer, and Potentially bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching product name in body, potentially bad keyword in body (194): Acidaburn the body by rainkohl on apple.SE
@ppwater It looks like it should be FP. But, I think the Mods there should let this room know about it. It seems that we didn't know. Can you tell the history about this post?
@SmokeDetector The state of Andhra Pradesh has reported 282 corona cases in the last 24 hours. One is dead. This was revealed by the government in the Health Bulletin on Saturday evening, December 26, 2020. Of the 42,911 samples tested, YSR said one died in Kadapa district. It revealed that 442 people had fully recovered from Kovid in the past 24 hours and 1,15,74,117 samples had been tested in the state till Saturday.
Bad keyword in body - Position 16-29: Testo Booster, Position 402-413: Muira Puama, Positions 663-676, 746-759: testo-booster, Positions 819-832, 914-927: Testo-Booster Bad keyword in title - Position 37-50: TESTO BOOSTER Blacklisted website in body - Positions 630-649, 713-732: fitnesscaremart.com Link at end of body - Link at end: https://www.facebook.com/Atomic-Shred-Testo-Booster-106133838070294 Pattern-matching product name in body - Position 16-29: Testo Booster, Positions 663-676, 746-759: testo-booster, Positions 819-832, 914-927: Testo-Booster
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-25: hindigalaxy0077.blogspot. Potentially bad keyword in title - Position 0-25: hindigalaxy0077.blogspot. Potentially bad keyword in username - Position 0-25: hindigalaxy0077.blogspot.
@ppwater The regex contains an unescaped "."; in most cases, it should be "\."; append -force if you really want to do that.
@ppwater That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answer; append -force if you really want to do that.
> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - sound-buttons.com NS suspicious n1.hosterpk.com.,n2.hosterpk.com. Potentially bad ns for domain in title - sound-buttons.com NS suspicious n1.hosterpk.com.,n2.hosterpk.com.
@ppwater 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.
