[ SmokeDetector | MS ] Bad keyword in username, blacklisted website in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in username, +1 more (263): How to get ISO 27001 Certification? by ISO BAHRAIN on ham.SE
@Mast 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, blacklisted website in body, link at beginning of body, link at end of body, potentially bad ip for hostname in body, +2 more (341): Blood Balance Formula Benefits: by bldblnce on meta.SE
@VictorVosMottor 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 link text in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, +1 more (458): Dissertation Writing Services by dorcassmith on math.SE
@VictorVosMottor 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 Google translation: "The copy of the song was written, but the money was deducted from the account, the copy of the song was a right download download registerd option"
maybe it means "I was charged for a failed download" or something?
@SmokeDetector PR 4953 was intended to catch metasmoke.erwaysoftware.com/post/266862 based on titles; the body search comes up empty. Let me know if I should do watch-title or something else
@JeffSchaller 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.
@VictorVosMottor 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.
Yeah, I'm not sure what was going on with the metasmoke instance. The console output just stops for the last 5 days, as does the auto-rebooting. However, it has been operational and posting feedback into chat during that time, until about 20 hours ago. As soon as I logged into the instance, it auto-rebooted and started posting feedback.
@DanielWiddis It was an auto-reboot, not manual. It's not listening to commands from here, as that would get confusing to have two instances listening to commands in the same room.
@Mast 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.
