1. [:40906406] <skipped> 2. [:40906369] Body - Position 78-91: credit repair, Position 174-193: professional hacker Body - Position 1098-1127: hack Android and many Contact Post - Keyword *credit* with email [email protected] Post - Pattern-matching email [email protected]
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body: Le Juve Raview? by lucyrshaffer on askubuntu.com
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +3 more: nitroshredadvice.com/xytropin/ by KaloKali68 on graphicdesign.SE
@tripleee That pattern looks like it's already caught by Pattern-matching website in answer, Bad ns for domain in answer, Bad ns for domain in body, and Pattern-matching website in body; use !!/blacklist-website-force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: Le Juve Raview? by lucyrshaffer on askubuntu.com
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +6 more: healthpluscogni.com/revglow-cream/ by pths on askubuntu.com
tpu- by suraj
[ SmokeDetector | MS ] URL in title, blacklisted website in body, blacklisted website in title, link following arrow in body, pattern-matching website in body, +1 more: brainfireadvice.com/focus-fast/ by Prnki Conz on apple.SE
CI on ca80137 succeeded. Message contains 'autopull', pulling...
[ SmokeDetector ] SmokeDetector started at [rev ca80137 (tripleee: Auto watch of (?<=[-/])focus\W?fast(?=[-/<"]) by tripleee --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/ca80137) (running on Henders/EC2)
@tripleee That pattern looks like it's already caught by Pattern-matching website in body, Bad keyword in body, Pattern-matching website in answer, and Bad keyword in answer; use !!/blacklist-website-force if you really want to do that.
any thoughts on a lighter website blacklisting process? I'm thinking we could have relaxed criteria for "current campaigns" where "current campaigns" is defined something like "multiple spam messages for multiple domains in the last ... what? 48 hours?"
@SmokeDetector k
we'd probably also want to have a process for removing stuff from campaigns which are no longer current, but that's already planned
as in, we should have a tool to remove patterns which are no longer productive
@tripleee Ideally we'd have something akin to a review queue on MS for that
Where patterns get put up for renewal / review with detailed stats on how they've been performing. At least for the streamlined blacklists that have been moved to file.
@Magisch how do you mean? I'm thinking it could probably be completely automated ... no hits in the last six months (or two years, or whatever) and we remove the pattern
but we should have a better understanding of how and when patterns recur