[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +5 more (794): supplementslove.com/folinu/ by Creap32 on askubuntu.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, blacklisted website in body, link at end of body, potentially bad ns for domain in body, +2 more (496): Does it have any manifestations? by hocherlon on meta.SE
[ 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 (590): Keto Power Diet Australia by flespldf on graphicdesign.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, body starts with title and ends in url, potentially bad ip for hostname in body, +3 more (392): www.hsbuy.org/nutriverse-keto/ by user148354 on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword in answer, pattern-matching website in answer, potentially bad asn for hostname in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (168): Can a user use neopronouns for any third party? by Amira Smith on meta.SE
@double-beep That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@Machavity Yeah, I know. It's one of the reasons I just went with the referral code, since those seemed to be unique to each spammer (at least the ones Smokey has caught so far). My question was whether we should remove the actual codes from the watch list, leaving your watch item to replace them
@SmokeDetector spam- This is a 'second strike yer out' case. User is promoting their paper and copy-pasting the same post on multiple questions. Doesn't even try to tailor their answer to the posts. While there is disclosure, this is excessive
@Das_Geek That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.