today in "regexes with a higher TP rate than they have any business having", with 4225 TP/478 FP/102 NAA: a href="[^"]+/(\w+-){2,}\w++/?"[^>]++>(?-i:(?:[a-z]++ ){2,}[a-z]++)</a
Will think on it a little while to see if I can do better than that
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, pattern-matching product name in body, pattern-matching product name in title, pattern-matching website in body, +1 more (459): Is Rejuv Boost CBD Formula Reviews? by tilli nake on astronomy.SE
This is something that I do not understand at all because the community tends to respond to spam extremely fast from what I have seen. It gets down-voted to oblivion and I can't see it staying in the site long enough for anyone to actually get a chance to click on their links.
However, I keep o...
@cigien they only collect attention when the post gets a relatively low weight; often they (inexplicably) seem to mix new domains with already deeply tarnished ones so we don't notice the new ones
Using the same dialect would be ideal. Though I don't see many people using hal for notifications, so cost/benefit ratio probably would be a bit too high to bother.
> Potentially bad ns for domain in body, potentially bad ns for domain in title, potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Potentially bad keyword in body - Position 0-12: keyquery.com Potentially bad keyword in title - Position 0-12: keyquery.com Potentially bad keyword in username - Position 0-12: keyquery.com Potentially bad ns for domain in body - keyquery.com NS suspicious ns44.domaincontrol.com.,ns43.domaincontrol.com.
@Mast No, generally, it means that at least one of us needs to raise a custom mod flag to explain why we are flagging something which, if you don't have any context and don't look for plagiarism, it looks like it might be OK. While I agree that the mods should do a bit more investigation when they are getting multiple spam flags on a post, it can easily be something where they don't do more investigation and only evaluate it based on what is displayed in the mod flag queue.
It can also be that the flags may come in sporadically and be handled in sequence, rather than all at once, which can give less urgency. In such cases, the mod flag queue shows that prior flags exist, but that they were dismissed, which can tend to bias mods to do respond in the same way to similar flags.
@JeffSchaller 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.
This is something that I do not understand at all because the community tends to respond to spam extremely fast from what I have seen. It gets down-voted to oblivion and I can't see it staying in the site long enough for anyone to actually get a chance to click on their links.
However, I keep o...
