[ SmokeDetector | MS ] Bad ns for domain in answer, blacklisted website in answer, potentially bad ip for hostname in answer, potentially bad ns for domain in answer (178): Creating a virtual serial port by Wendy Li on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword with email in body, bad phone number in body, blacklisted website in body, potentially bad keyword in body (348): Successful Funds Recovery by user291921 on security.SE
!!/report stackoverflow.com/q/74947265 "Incomprehensible title, nonsense body, unexplained image. If this is a question, I can't even begin to guess what they're asking."
@RyanM the Snyk promotion is probably part of the regular output from a software tool, I see something similar in the output from Docker build but this looks slightly different
@user16217248 While that's not incorrect, note that someone editing it would mark that flag helpful without moderator action. If you were under 3k I'd say to flag to close instead, but since you can close vote, you can both flag and vote to close as unclear. As far as flagging...oh, I dunno, probably most things are fine. VLQ is fine, R/A is honestly fine (it's really nonsense), and a custom flag saying "This looks like there might have been an attempt at a question, but it's mostly gibberish; could you delete it?" would be fine.
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
Makyen/EC2-linux received failover signal. <-- This probably shouldn't have happened. Check if Thoth is operational (e.g. !!/location) and consider executing !!/standby Makyen/EC2-linux to put this instance back in standby. (@Makyen)
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
