[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body: Where to buy enduraflex by Alonewolf on graphicdesign.SE
@tripleee That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Blacklisted website in answer, pattern-matching website in answer, potentially bad keyword in answer, blacklisted user: rbind in a loop in R by KateSmith on stackoverflow.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: Intense X Male Enhancement by user85045 on drupal.SE
halflife:2018-04-25 12:46:39,001:https://is.gd/gotrdbot redirects to https://www.binbotpro.com?utm_source=affiliates&utm_medium=referral&utm_campaign=register&utm_content=40&utm_term=543
that looks extremely suspicious; I will flag as spam
googling for binbotpro gets me a boatload of scam warnings
github.com/Charcoal-SE/SmokeDetector/pull/2094 proposes an experimental rule for "bad NS" experiments; this is currently a hard-coded list of name servers I hope to be able to decide on either fully blacklisting or removing once we see the hit rate
@doppelgreener That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body; append -force if you really want to do that.
but you still need to understand how the engine will try every possible loophole to produce a match and find one if there is a way, so expressions with lookaheads are sometimes hairier than just "not this"
the first two questions are really "which tool are you using" and "does it really force you to use regex for this?" ... many times people try regex101 and then notice that it doesn't speak exactly the same dialect as the tool they actually want to use
look, there's this Java implementation in peanut butter and corn flakes which needs to parse an XML file which is full of engine oil and rust ... to produce a PHP site with a friendly interface to MySQL where we have all our credit cards and passwords
Most of the SE sites are down for few mins, but MSE is working fine.
