I'm new, and I want to: "Get yourself familiar with what goes on there; chat to some of the regulars about the system, and you’ll figure out how to get involved."
@iBug Welcome to Charcoal HQ @Devealte! I'm SmokeDetector, a bot that detects spam and offensive posts on the network, and posts alerts to chat. You can find more about me on the Charcoal website.
@Devealte We're a voluntary team that helps the Stack Exchange Network fight off spam and offensive content, with the help of this bot that we have developed and are maintaining.
@Devealte Make sure you know what spam flags and R/A flags are for, and you've read our feedback guidance. Then I can add you to SmokeDetector's privilege list
@Devealte Welcome. TL;DR: If Smokey reports a spam post, flag it as spam and the correct feedback is k; if Smokey reports something that isn't spam, the correct feedback is f.
You send that feedback by replying to Smokey's message, like so:
Adding to that, sometimes Smokey catches vandalized post. Use v as the feedback to vandalism.
Pro tip: Check for a pencil emoji when looking at reports - it means the post is edited at least once. Newly-posted ones don't have that pencil indicator.
@SmokeDetector I am borderline on this one. Part of me thinks it may just be a misguided user - and the other part of me thinks it could be spam. I think it's at least worth watching the link since the only reason this was caught was as it was at the end of the post - but I am refraining from providing FB atm.
@K.Dᴀᴠɪs Please use neither. In general (and if it works for the detection you desire), try to limit the .* to some finite number (e.g. .{0,20}?, so that it restricts topicality and doesn't spend as much resources testing out the the end of the post. In addition, particularly with large repeat numbers, or unbounded, it's best to use non-greedy, so that it finds a closer match (if that fits your needs). For instance, up\W*a\W*cup.{0,20}?(?:breast|pills|bust|cream)s? gets 15TP and 0FP.
Give me a few minutes to refine it, as there's another TP that should be detected that I need to track down.
As to using look-ahead/look-behind, the primary reason is to keep that part out of the why text. In this case, it's helpful to the user to see the (?:breast|pills|bust|cream)s, so it's better to have it not in a look-ahead.
@K.Dᴀᴠɪs That's going to depend on the implementation. In theory, there should be no difference.
I haven't done any benchmarking for the Python implementations, so I can't really say. The logic for a single positive look-ahead is very similar to just having a non-capturing group. Depending on how both the code and regex are written it may be more or less.
@K.Dᴀᴠɪs That pattern looks like it's already caught by Pattern-matching email in answer and Pattern-matching email in body; append -force if you really want to do that.
@iBug That's specifically double-dipping (blacklist) detection reasons for that number. We really should not be doing that. IMO, we definitely shouldn't be doing it for something we've only detected once, even when there's a very low chance of FP.
@TetsuyaYamamoto 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.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, potentially bad keyword in body (296): Do not skip meals. When you by imranrao on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, potentially bad ns for domain in body (390): Brain Plus IQ Review by qpadaas on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +2 more (688): Naturaful Breast Enlargement by nikkiwikki4488 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, potentially bad keyword in body, +1 more (396): Bio X Keto Some foods like simple sugars, by jilpqxvu on ham.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more (492): Radiantly Slim Australia by aplozappolas on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +1 more (491): Test Troxin Canada by hopsnadi on superuser.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching product name in body, +2 more (590): Nutrisystem Diet by user90386 on drupal.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +7 more (990): evaherbalist.com/luma-slim/ by Podwgnxo on askubuntu.com
@Glorfindel That pattern looks like it's already caught by Potentially problematic ns configuration in answer and Potentially problematic ns configuration in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +3 more (563): This is the tropical natural Purefit Keto by imranrao on askubuntu.com
[ 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): Alpha Size Fuel Alpha Size Fuel by qpadaad on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, potentially problematic ns configuration in body (422): Nuhydrate serum canada by amabellacream1 on meta.SE
Why the "we"? Are you writing on behalf of Chelsea Motorcycles? I note your answer's wording closely correlates to their FAQ item on the matter—please see our promotion guidelines which require disclosure of affiliation. — doppelgreener1 min ago
[ SmokeDetector | MS ] Bad keyword with email in answer, potentially bad asn for hostname in answer, username similar to website in answer (138): SPSS Modeler, Hadoop by Stat Aanalytica on stackoverflow.com
tpu- by Shree
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +7 more (987): evaherbalist.com/luma-slim/ by Wynkzkcr on drupal.SE
