@SmokeDetector The question was asking for resources. The linked site/product doesn't really appear to do what is asked, but I'm going to give it the benefit of doubt.
@Mr.YouKnowWhoIAm It has authorization restrictions as you move through the required links. Only the list of authorized users should be able to complete the action and actually be effective at clicking the final button.
@Mr.YouKnowWhoIAm I have a lot of site-themed display names
For example, on Meta it's as you've noted, on Apple.SE I'm iBug with Retina Display, on Physics I'm Schrödinger's iBug, on French Language I'm iBug aux erreurs, etc.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +9 more (987): nutritionless.com/keto-lean/ by aopugeoz on drupal.SE
My second instance is on DigitalOcean Droplet, which should have unlimited CPU usage (as opposed to AWS's "CPU Credit" rules). I'm planning to suspend hosting Smokey on my AWS server until I get a more powerful instance.
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +9 more (990): nutritionless.com/keto-lean/ by aopugeoz on askubuntu.com
That sounds reasonable. Based on how the AWS CPU credits work, and being on the free tier, I've been concerned about running out of CPU credits when my instance has become active and remained active for some time. It's appeared it would be necessary to have at least two instances ping-ponging back and forth or automatically stop and start the instance to get the 30 credits for startup.
@SmokeDetector This ended up with 4 detection reasons based on effectively the same content. The body content was bad and detecting it is good. However, it's still 4 closely related reasons, which feels a bit much in this instance.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, potentially bad ns for domain in body, potentially bad keyword in body, +2 more (296): holistic bliss keto by hstb2ch on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in link text in body, bad pattern in url body, pattern-matching website in body, potentially bad keyword in body (259): Print spooler in Windows 10 by Hilary Duff on superuser.com
@Shree 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, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, +1 more (489): https healthjudges com keytone diet uk by CasJohns on graphicdesign.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, body starts with title and ends in url, link at end of body, +4 more (491): medhush.com/level8-keto/ by kabesha12 on workplace.SE
@double-beep That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer; append -force if you really want to do that.
@double-beep 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.
PR#2940 ("double-beep: Watch topessayservices\.com") opened by SmokeDetector
@double-beep That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, pattern-matching website in body, potentially bad keyword in body, +1 more (396): *BEFORE BUYING*: (UPDATES May 2019) Max Fit Keto! by sooekoe on drupal.SE
tpu- feedback received
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +8 more (888): nutritionless.com/keto-lean/ by nghtiaskl on wordpress.SE
