@Vickel The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, bad keyword in link text in body, blacklisted website in body, pattern-matching website in body (458): Best Stock Broker in India by Best stock Broker on meta.SE (@Ollie @Ethan)
!!/report stackoverflow.com/a/77637620 "Undisclosed affiliation; about page on youtube lists owner as instagram.com/amolkapadi which is the same as SO username"
!!/report stackoverflow.com/a/77637518 "Undisclosed affiliation; about page on youtube lists owner as instagram.com/amolkapadi which is the same as SO username"
@Nick 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 word(s) if you really want to add the pattern you provided.
@Jesse 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 word(s) if you really want to add the pattern you provided.
@Jesse The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ Based on the logo on the website, I think it's "Hi Velance", or potentially just one word as it is in the post. And yes, it is very rude of them.
I swear I searched chat for "skillzee" to see if it was already watched. I guess I didn't, maybe searched for "skillzee." or something because there were no results.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, potentially bad asn for hostname in body, potentially bad keyword in body (265): Apple Service center Kochi by Jeejesh Maniyalath on serverfault.com
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad keyword in body, potentially problematic ns configuration in body (100): Hire Nodejs Developers by Anil Gupta on stackoverflow.com
[ SmokeDetector | MS ] Link at end of answer, potentially bad ns for domain in answer, potentially bad keyword in answer, potentially bad keyword in username, username similar to website in answer, +1 more (207): Disappearing index.html and index.php by Bakemate on serverfault.com
@VLAZ The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
^ from metasmoke.erwaysoftware.com/post/453460 I "unrolled" the [\W_] to [^a-z0-9] which is the equivalent, so I could exclude an additional token. See regex101 for the match: regex101.com/r/fGw6nT/1 I'm not sure if it's actually worth watching, though. I'll leave it be, if anybody feels it should, then maybe run that with a -force
