@tripleee That pattern looks like it's already caught by Bad ns for domain in answer and Bad ns for domain in body; append -force if you really want to do that.
@tripleee Matched by (?:[a-z0-9-]{1,40}?scrabble[a-z0-9-]{0,40}?|[a-z0-9-]{0,40}?scrabble[a-z0-9-]{2,40}?)\b(?!\.vip(?<=scrabblewordfinder\.vip))(?!\.weebly\.com(?<=officialscrabbledictionary\.weebly\.com))(?!\.blogspot(?<=scrabblewordfinders\.blogspot))(?!\.yolasite\.com(?<=officialscrabblewordfinder\.yolasite\.com))(?:\.[a-z0-9-]{1,40}?)+ on line 13896 of watched_keywords.txt
Ugh... I request a addition to SE's built-in spam filter considering SE is getting a significant quantity of "Keto" spam, and someone answers saying "Meh, SD is catching all spam just fine on Drupal"...
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Das_Geek 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.
@Makyen We should probably not immediately !!/approve PRs. Doing so causes CI to fail, due to the branch being deleted prior to either CI trying to check it out. Waiting a minute, or two, would probably be helpful. There's little likelihood of negative impact on SD for a rapid !!/approve, but it does make the PR look like it's failed CI. [Note: I've manually undeleted the branch and re-run the Circle CI, which passed (no surprise), but there doesn't appear to be a way to rerun Travis.]
@Das_Geek That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.