[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in username, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in username (291): How to Registration for ISO 9001? by ISO BAHRAIN on rpg.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at beginning of body, potentially bad asn for hostname in body, potentially bad ns for domain in body, +2 more (313): What is CORS? How does it work? by RehanaS on askubuntu.com
@sau226 That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; append -force if you really want to do that.
nope, they are just strings, though this can get confusing too, unless you use raw strings (first you have to escape things in the Python string, then you need to escape them from the regex engine)
@Mast Matched by ^.{1,15}?cream(?<!icecream)(?<!ice[\W_]cream)(?<!^bluescream)(?<!^bluscream)(?<!\bscream)(?<!^colorscream)(?<!\bhellscream)(?<!^wolfscream)(?<!^eyescream)(?<!^starscream)(?<!^olscream)(?<!^dreamcream)(?<!^stealthscream)(?<!^krispycream)(?<!^cameocream)(?<!^coffeewithcream)(?<!^soft cream)(?<!^handcream)(?<!^doughnut facecream)(?<!^doncream)(?<!^Mayocream)(?<!^willcream)(?<!^bfdicream)(?<!^coder_scream)(?<!^confused_scream)(?<!^ice7cream)(?<!^iscream)(?<!^isecream)(?<!^mikacream)(?<!^paul cream)(?<!^sadscream)(?<!^spinescream)(?<!^sscream)(?<!^testscream)(?<!^whipcream)(?<!^whyscream)$(?#add additional exclusions as more legit users are detected) on line 4401 of watched_keywords.txt
@tripleee Extra backslashes are convenient when one wants to be able to just copy and past it into different environments, some of which require the backslash on a /, whereas none of them operate incorrectly when there are extra backslashes. Having the extra backslash makes for less work and fewer errors when moving it around. I'm not saying we should have a policy of using them, just explaining why some of the regexes I write have them.
(also, in case this looks passive-aggressive quoting a message at you that was originally sent to you: I honestly did not notice until I sent it, and no such subtext/meaning was intended)
@Mast 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.
@VictorVosMottor this report that you gave naa feedback on is quite likely spam. Note that it was for a blacklisted user and the user's previous post also linked that same site. I also noted a few other hints in my comment.
@VictorVosMottor That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, +5 more (638): Keto Premiere South Africa by seanghl on graphicdesign.SE
