[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (394): Gidae Cream Cream by Lelxberxksde on askubuntu.com
> Bad keyword in body, bad keyword in title, bad keyword in username, few unique characters in body, repeating words in body, repeating words in title ---------- Title - Positions 0-9, 10-19, 20-29, +14 more: forskolin Title - Repeated word: *forskolin* Body - Positions 0-9, 10-19, 20-29, +14 more: forskolin Body - Contains 9 unique characters Body - Repeated word: *forskolin* Username - Positions 0-9, 10-19, 20-29, +14 more: forskolin
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Positions 0-9, 10-19, 20-29, 30-39: forskolin Body - Positions 0-9, 10-19, 20-29, 30-39: forskolin Username - Positions 0-9, 10-19, 20-29, 30-39: forskolin
@iBug That pattern looks like it's already caught by Bad ns for domain in body and Bad ns for domain in answer; append -force if you really want to do that.
@JoErNanO 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.
@Glorfindel 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.
LOL, I downloaded a software and during account registration, I supplied "Hogwarts School" as Company or Organization, and in the Subject box I filled in "Wizardry"
[ SmokeDetector | MS ] Blacklisted username, offensive answer detected, potentially bad keyword in answer, toxic answer detected (258): Unicode mirror character? by fuck u on stackoverflow.com
@Makyen That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@EriktheOutgolfer Ahh, OK. I guess I missed it, in part because I'm familiar with FIRE's internals. FIRE doesn't actually send "rude" as feedback. While "rude" is shown in the UI, it's translated to tpu- before transmitting it to MS via the API.
@Makyen That pattern looks like it's already caught by Bad keyword in answer, Phone number detected in answer, and Phone number detected in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Bad keyword in answer; append -force if you really want to do that.
The above SD complaints are partial matches or matches on the comment text, which don't actually match the things actually being added to the watchlist.
@SmokeDetector I'm not sure what I'd call this. The original content wasn't an answer either.
@iBug Yes. I was trying to provide some record of why I overrode the complaints/checks. In general, we have people learning how to use the commands. In some cases, this has resulted in overriding similar checks when it wasn't appropriate. I wanted to indicate that overriding the checks wasn't just an automatic response, but that consideration was put into why the checks failed and the appropriateness of overriding them.
