@SmokeDetector previous post by OP was flagged as TP, this one was deleted from the site, presumably closed as spam by the site's users -- thus I'm calling this TP too (currently 4/4, next TP hit will merit blacklisting)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad asn for hostname in body, potentially bad keyword in body, potentially bad keyword in title (196): Digital Marketing Company in Kerala by Athira on stackoverflow.com
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command if you really want to add this pattern.
[ SmokeDetector | MS ] Link at end of answer, potentially problematic ns configuration in answer, username similar to website in answer (128): Remove oddly nested substrings by Webwooter on codegolf.SE (@hyper-neutrino)
@Dudecoinheringaahing I can't find a better note right now, but that notification is per-instance of SD, so if/when it fails over, you'll have to re-send the command. (I think)
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (3): .WOFF fonts not linking by Scott McDaniel on stackoverflow.com
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@SmokeDetector slightly hesitant, but hard to see how it adds any value or even means anything, other than as a way to link to a site which seems to have no direct relationship to the topic of the question
