@Makyen 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.
@Makyen 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.
@Makyen 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.
@tripleee The regex contains an unescaped ".", which should be "\." in most cases. 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 body and Potentially bad keyword in answer Append -force to the command if you really want to add this pattern.
@RyanM @tripleee I added a slightly more specific watch here; up to you if you want to cover any appearances of the last name, but you probably want to remove the redundant watch if so
@SurajRao but they took out the promotional link, so it could be that they learned their lesson and are now merely trying to post a low-quality but legitimate answer
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at beginning of body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, +1 more (237): Thankyou for service by vijay joseph on homebrew.SE
@metasmoke ... complete with a typo in the commit message /-:
I unwatched this IP address, it had only one TP hit over almost three weeks and lots of FP ... though it sucks a little, because the one TP had no other detections metasmoke.erwaysoftware.com/post/322805
