[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted username, body starts with title and ends in url, pattern-matching product name in body, +4 more (682): Purefit Keto Diet Reviews by mexonjuriya on webapps.SE
When reviewing a post that was found by the "link at end of answer" rule, I should just review like any other, marking it as a false positive if the link was fine, right? I mean, it was a true positive in the sense that a link was indeed found at the end of the answer, but marking it as true for that seems pointless.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, pattern-matching website in body, +3 more (560): Away with fatty acids and absolutely by user163808 on wordpress.SE
@tripleee I am reviewing a question that was posted on AU in Turkish. Google Translate suggests the question is OK, but of course, it should be closed/deleted since it isn't in English. It was caught because it mentioned a link that pointed to one of the bad name servers. So I will be marking as a false positive since the link was fine, despite the question having serious issues. That's the desired behavior, right?
2
On the one hand, we would actually want to catch such posts, but on the other, not for the reason given.
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, pattern-matching product name in body, +6 more (792): supplementeffects.com/hard-boost-xl/ by nekasipoz on wordpress.SE
@terdon the "bad NS" reason is a pretty big hammer, it generates a fair amount of FPs (but like many of the reasons we keep, the FPs are tolerable for the value it provides ... I hope, still)
@tripleee That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Pattern-matching website in body, Blacklisted website in body, Blacklisted website in answer, and Pattern-matching website in answer; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@tripleee 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.
@DavidPostill Post 1: Already recently reported [ MS ]
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +6 more (791): Keto Blast Weight Loss Pills by Beall11 on workplace.SE
@EriktheOutgolfer In response to !!/watch or !!/blacklist-*, seeing any of the "already caught" reasons impling an existing watch or blacklist means something like "you shouldn't add this ... unless you really know why you are seeing this message and have considered what the overlap is." In general, that means that you've, at least, gone and looked at the contents of the existing lists and determined exactly what is being caught, or not. The !!/bisect and !!/test commands help quite a bit.
