> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username, potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Potentially bad keyword in body - Position 0-14: moneyguides.in Potentially bad keyword in title - Position 0-14: moneyguides.in Potentially bad keyword in username - Position 0-14: moneyguides.in Potentially problematic ns configuration in body - Suspicious nameservers: all IP addresses for moneyguides.in are in set {'51.210.3.223'}
[ SmokeDetector | MS ] Pattern-matching website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (81): Converting a PDF to PNG by lauriii on stackoverflow.com
@VictorVosMottor Per "If SmokeDetector was implemented as a system-level block, would we want to catch this type of activity?" the answer would be yes so in theory it should be k/tp.
@Xnero This is the problem with the "system level block" metric - if you take it too far, you go "well, we'd like to block everything that's not good quality content"
I haven't been able to come up with a better guideline
(I'm assuming the Google translate is close enough to right)
user435118
@Undo I speak Russian and it's "How do you add ZIP?".
In short, NAA is a feedback type because it exists in that strange gray area between "good content" and "spam". Other projects (SOBotics) try to detect bad- or non-answers, we only want spam.
@Xnero 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.
@VictorVosMottor 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.
@VictorVosMottor 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, link at beginning of body, potentially bad ip for hostname in body, potentially bad keyword in body (143): How to invest money by M. Ibrahim on stackoverflow.com
@Yatin I'm not sure we should add the watches in PR#5878 and PR#5882. They both generate quite a few FP, on SE and MS, so it's unlikely we'd ever blacklist either. The issue with the Spam posts is the OP promoting their products, and so we should probably try to catch that. Which it seems we can do with the username in this case.
@SmokeDetector It's a real name, but there's only one network account with that username currently (and it has no valuable posts), so we're good for now.
