[ SmokeDetector | MS ] Bad keyword in body, bad phone number in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad ns for domain in title (296): Custompins.ca Company by Amy Jade on superuser.com
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad ip for hostname in answer, potentially problematic ns configuration in answer (36): Asus laptop Macro keys mapping by drivers on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, potentially bad keyword in body, potentially bad keyword in title (293): Cheyenne Valley CBD Oil by TeagaKonop on apple.SE
@SmokeDetector @Makyen Why was your instance still running even though it received a failover signal? This resulted in two instances running for a brief period of time.
Getting a failover signal when there's already an instance running usually implies there's an issue with MS. That would be also implied by the errors I see in the Makyen/EC2-num02 instance console. I don't see any in the EC2-linux console, because there was enough output to have resulted in any such errors at about that time no longer being in the console buffer.
these "filezilla for mac" posts have a really weird way of linking to ... whatever it is that they are linking to. It looks superficially like it would be a link to Filezilla actually, but I guess it isn't (and I'm not particularly eager to click through)
@Makyen Could you explain why you've added this watch? I know what it catches (I think), but I'm not sure why we want to do that, especially because there's already a watch for crackcool\.com. Is it so that there's a separate watch for the website, and the keyword? If so, why not just watch crack[\W_*]cool\.com instead of the version you wrote?
@cigien It is a bit malformed. It looks like I didn't double-check what the script produced, even though I should have done so, given the input which I'd provided to it.
@cigien Yeah, it's a relatively common formulation. The script I use will create it automatically when both the hostname and some things that match the second level domain are fed into the script at the same time. In this instance, I actually had three very similar entries fed into the script when it was activated, rather than only two.
I was performing a test and then briefly got pulled onto something else in the real world, but didn't double-check the results well, at all, once I got back to it. So, overall, it's my fault/error.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, potentially bad asn for hostname in body, +3 more (465): keto Wave Diet Pills by verbinal werki on math.SE
@tripleee That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Few unique characters in body, mostly punctuation marks in body, mostly punctuation marks in title, repeating characters in body, repeating characters in title, +1 more (372): //////////////////////////// ✏️ by user238169 on english.SE
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer (169): How much shrimps? by david martin on ell.SE
