@Makyen I figured you were probably tweaking and all the others are working (good thing to have more than a few running in standby) so I knew it wasn't an emergency; but I thought it was worth a ping. You are welcome.
@Rob Yeah, recently there have been a few times where either I've been uncomfortable with the low number of SD instances running, or where we've even had no instances running. I decided that I'd feel more comfortable with at least one instance which I can kick/reboot myself. Having an instance of my own also gives me the opportunity to play around with more complex things in SD than just regexes (i.e. learn Python), which is beneficial.
The first EC2 instance I brought up had the normal slog through things not acceptably configured in the OS. So, I also wanted a (mostly) copy-&-paste-able set of commands to go from a new EC2 linux instance to being able to run SD.
once upon a time, there was but one Smokey instance running at a time, and it was the One True Smokey
and it was hosted upon a crappy old laptop hidden away in a crappy old closet, and the gods of technology looked down upon it, and saw that it was good, and did name it ClosetServer
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-13: Sugar Balance Username - Position 0-13: Sugar Balance Body - Position 0-13: Sugar Balance
@Makyen The computer CPU I'm waiting to be publicly available (EPYC 2, 7nm) has encrypted export to server hardware support so I'll be able get everything set up at home and export running instances easily. I'll know it will run and has been tested/tweaked (locally, at least) and so it is supposed to 'just work™' when it hits the other side. It's just a long wait for a fast SKU to be released, I don't need 64 cores but a 1/3rd that many at 5Ghz would be
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (394): Why does coronary heart price topic? by hcryrpoe on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, +1 more (394): Do that each morning and you are going by maciah on drupal.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more (791): pilpedia.com/azur-derma/ by sexitegod on askubuntu.com
> Potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Title - Suspicious nameservers: all IP addresses for stubmuster.com are in set {'94.130.187.36'} Body - Suspicious nameservers: all IP addresses for stubmuster.com are in set {'94.130.187.36'}
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially problematic ns configuration in body and Potentially problematic ns configuration in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body (392): male enhancement by countgh on wordpress.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more (791): pilpedia.com/azur-derma/ by tempa201 on askubuntu.com
Autoflagged FP: flagged by @SmokeDetector, @CalvT, @ByteCommander
tpu- feedback received
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, potentially bad asn for hostname in body, +2 more (396): dietpillspapa.com/prache-cream/ by PracheCream on biology.SE
[ SmokeDetector | MS ] Blacklisted website in answer, pattern-matching website in answer, potentially bad asn for hostname in answer (173): Bulk edit emails header by rick1221 on superuser.com
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially problematic ns configuration in body, Pattern-matching website in answer, Potentially bad keyword in body, Potentially problematic ns configuration in answer, Potentially bad keyword in answer, and Pattern-matching website in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially problematic ns configuration in body and Potentially problematic ns configuration in answer; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@TetsuyaYamamoto 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.
@tripleee That pattern looks like it's already caught by Potentially problematic ns configuration in body, Pattern-matching website in answer, Potentially problematic ns configuration in answer, and Pattern-matching website in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@tripleee That pattern looks like it's already caught by Bad keyword in body, Bad keyword in answer, Blacklisted website in body, and Blacklisted website in answer; append -force if you really want to do that.
[ 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 (592): Keranique Hair Regrowth by kathleenrlivingston on drupal.SE
@tripleee That pattern looks like it's already caught by Pattern-matching website in answer, Bad keyword in answer, Bad keyword in body, and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more (692): pilpedia.com/keto-primal/ by zabinoba on askubuntu.com
@SmokeDetector I find it implausible that a dryer ventilation customer would spontaneously exhibit this level of enthusiasm and technical detail while linking to the advertised web site multiple times
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more (792): pilpedia.com/keto-primal/ by asihqnia201 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link following arrow in body, +2 more (588): Hydra Life Serum by lionykity on apple.SE
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, bad keyword in username, blacklisted website in body, +9 more (884): fitose.com/slim-quick-keto/ by Slim Keto on academia.SE
@Undo MS appears to be running slow, and Smokey is running into timeouts every now and then. Hopefully this is a preemptive ping and everything will sort itself out, but maybe it's worth taking a look at
[ 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, +5 more (593): www.epbhub.com/tone-keto/ by moddeuskaz on graphicdesign.SE
