[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (200): Can you run gambling ads on Facebook? by Gambling ads on meta.SE (@Ollie @Ethan)
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, potentially bad keyword in answer (170): Fibonacci Binary Squares by vijay on codegolf.SE (@cairdcoinheringaahing @lyxal)
[ SmokeDetector | MS ] Linked punctuation in answer, potentially bad asn for hostname in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (77): How should we deal with Google questions? by Btshoodieforwoman on meta.SE (@Ollie @Ethan)
@SmokeDetector Needs debugging details IMO, and SO users are unlikely to help them with just a link, but it doesn’t appear to be spam or asked in poor faith
[ SmokeDetector | MS ] Link at beginning of body, potentially bad asn for hostname in body, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username (45): Find the Perfect Android App with Findapk by FindApk on stackoverflow.com
@Pilot6 That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad keyword in link text in body, potentially bad keyword in body, potentially bad keyword in username, potentially problematic ns configuration in body, blacklisted user (143): How to find the web developer uk by Ficode Technologies on softwareengineering.SE
