[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, blacklisted user (240): How to splice several strings by isla on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted username, blacklisted website in answer, potentially bad ip for hostname in answer (184): Is gzip atomic? by jack miller on unix.SE (@Pandya)
[ SmokeDetector | MS ] Bad keyword in link text in answer, potentially problematic ns configuration in answer, username similar to website in answer (145): SFP+ on Juniper EX3300 by Sanso Network on networkengineering.SE
@Rubiksmoose 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.
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in username, potentially problematic ns configuration in body, blacklisted user (173): Why is Software Testing required? by kirankumarpaita on sqa.SE
[ SmokeDetector | MS ] Link at end of answer, potentially bad keyword in answer, potentially bad keyword in username, username similar to website in answer, blacklisted user (197): Am I too old? Is it too late? by filmyduniya on music.SE
@JohnDvorak We had a watchlist item not long ago that caught <strong>(LINK)</strong> (or something similar) and it had an astonishingly high FP rate. I expressed a degree of frustration when I ran into ~5 FP in a row, and at some point, it was unwatched. I'll dig up some context if I can find it relatively easy through the chat transcript.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, potentially bad keyword in body (261): adadadfdafdafadfadfdf ✏️ by Xeno on academia.SE
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 16:31:30 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/1482728
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 16:31:44 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/3815
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 16:31:59 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/117746
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 16:32:13 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/3852631
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 16:32:27 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/130837
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 16:32:41 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/26627
