@Makyen Added [A-Za-z_]*(1_)?859[\W_]*203[\W_]*2241[A-Za-z_] to watchlist
CI on 02df4e0 succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at [rev 02df4e0 (SmokeDetector: Auto watch of [A-Za-z_]*(1_)?859[\W_]*203[\W_]*2241[A-Za-z_]* by Makyen --autopull*)](//github.com/Charcoal-SE/SmokeDetector/commit/02df4e0) (running on teward/Solar Flare)
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted username, offensive answer detected, potentially bad keyword in answer, toxic answer detected: Heaven and Hell by Charles Rane on islam.SE
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 1-19: besttransmitter.co Body - Position 1-19: besttransmitter.co
A thought: a decent proof of concept for a multiple-site Smokey would be Reddit. Its API works base on a certain number of requests per minute, so polling /r/all/new.json and then fetching the posts wouldn't be feasible -- but there's another service that provides a websocket stream
@quartata Sure is. I mod a sub over there, and yeah while there's some content that Reddit itself just won't allow, beyond that I can define what's acceptable.
But I guarantee you there's plenty of pharma spam out there. That wasn't my point though. I meant it as an implementation exercise since it's similar to SE structurally
If you want and if the review stuff makes sense in my head, I can try adding some of the queues that need adding. Possibly those could go in an issue checklist?
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +1 more: mumybear.com/rapid-tone-diet/ by haniabee on askubuntu.com
> Bad ns for domain in body, bad ns for domain in title ---------- Title - freeleakdl.us NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com. Post - freeleakdl.us NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com.
Amazon finally got back to me on a ticket I submitted Apr 24; they have apparently taken some sort of action on asha24.com (though the domain is still hosted on AWS as of now)
@tripleee That pattern looks like it's already caught by Pattern-matching website in body, Bad keyword in answer, Pattern-matching website in answer, and Bad keyword in body; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Bad ns for domain in answer and Bad ns for domain in body; append -force if you really want to do that.
[ SmokeDetector ] SmokeDetector started at [rev 05013d6 (SmokeDetector: Auto blacklist of (?:\b|\w)(?:o(?:[^A-Za-z]|&#?\w+;)*)(?:d(?:[^A-Za-z]|&#?\w+;)*)(?:u(?:[^A-Za-z]|&#?\w+;)*)(?:d(?:[^A-Za-z]|&#?\w+;)*)(?:u(?:[^A-Za-z]|&#?\w+;)*)(?:w(?:[^A-Za-z]|&#?\w+;)*)(?:a(?:[^A-Za-z]|&#?\w+;)*)\w*(?:\b|\w*) by Makyen --autopull*)](//github.com/Charcoal-SE/SmokeDetector/commit/05013d6) (running on teward/Solar Flare)
