wait that's not what the guidance says right? "Treat these as you would an English post....Being in the wrong language for the site alone doesn’t make a post k-able."
Oh, I see the misunderstanding...yeah, the bit I quoted changes the "Treat these as you would an English post" slightly, rather than simply clarifying it.
It's basically "translate to a language you can read and then use that to judge whether it's tp or naa, but if it's the wrong language it's always at least NAA"
@Rubiksmoose np. It really just means we need to clarify how it says what's intended. Communication is almost always the responsibility of everyone involved.
@thesecretmaster I have code ready to merge for this. However, there were similar issues in multiple parts of the MS JavaScript. It's a bit more than I'd like to push to prod late on Friday/early Saturday. I expect I'll merge it when I get back in tomorrow.
@Makyen 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 Matched by ^.{1,15}?cream(?<!icecream)(?<!ice[\W_]cream)(?<!^bluescream)(?<!^bluscream)(?<!\bscream)(?<!^colorscream)(?<!\bhellscream)(?<!^wolfscream)(?<!^eyescream)(?<!^starscream)(?<!^olscream)(?<!^dreamcream)(?<!^stealthscream)(?<!^krispycream)(?<!^cameocream)(?<!^coffeewithcream)(?<!^soft cream)(?<!^handcream)(?<!^doughnut facecream)(?<!^doncream)(?<!^Mayocream)(?<!^willcream)(?<!^bfdicream)(?<!^coder_scream)(?<!^confused_scream)(?<!^ice7cream)(?<!^iscream)(?<!^isecream)(?<!^mikacream)(?<!^paul cream)(?<!^sadscream)(?<!^spinescream)(?<!^sscream)(?<!^testscream)(?<!^whipcream)(?<!^whyscream)$(?#add additional exclusions as more legit users are detected) on line 4402 of watched_keywords.txt
[ SmokeDetector | MS ] Potentially bad keyword in answer, potentially bad keyword in username, potentially problematic ns configuration in answer, username similar to website in answer (66): "Technology" vs. "a technology" by Newsronic on english.SE
@Mast 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.
@Mast 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.
// Interesting room, I have been creating such bot for SE to find bad questions, users, to watch 'em etc. but now I found out there is already one... ;)
Matched by the following regexes: shop now on line 9868 of watched_keywords.txt (?:order|shop|special)\W(?:today|now|offer)(?<!order\Worder) on line 9870 of watched_keywords.txt
