[ SmokeDetector | MS ] Bad keyword in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (396): They want to remove by user155928 on wordpress.SE
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, repeating characters in body, repeating characters in title (325): Solvedddddddddddd ✏️ by Jaja on stackoverflow.com
@SmokeDetector The link in this answer is to a .zip file on some 3rd party site, not the official Logitech site. The name of the domain used in this answer appears to be intended to confuse users. I'd consider this download to likely be malicious.
@K.Dᴀᴠɪs - They only have three posts remaining, and each contains a comment from the Review Queue saying: "While this link may answer the question link-only answers ...". My Custom Mod Flag is still pending. It is now the following day, your quota of flags will be refilled.
@Undo Code changes for metasmoke currently awaiting deploy include Blazer+config updates, so it'd be wise to go through manual deploy so you can fix things when they go wrong.
Needs a bundle update and for you to merge config/blazer.sample.yml into config/blazer.yml
@Makyen - You wrote a comment here explaining that the answerer ought to disclose their affiliation - that user hasn't returned, their profile is incomplete, and another user edited the answer to provide the information that you requested. I guess they are clairvoyant. I'll leave this with you since you are familiar with the history.
@Shree Yes, but many of the questions are specifically asking for recommendations, and the user at least minimally discloses affiliation in a few of the answers. Many of the questions should be closed, but are not appropriate for cv-pls requests in SOCVR.
[ 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, +2 more (492): Male Enhancement tablets by pkqzlaoho on drupal.SE
[ SmokeDetector | MS ] Body starts with title and ends in url, link at end of body, pattern-matching product name in body (296): Renegade meta pro by briangland on drupal.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching product name in body, potentially problematic ns configuration in body, +1 more (494): Presentation Of Testo Ultra by monitube on askubuntu.com
@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 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, body starts with title and ends in url, pattern-matching product name in body, +6 more (791): Keto Ultra Diet by johnbrillp on apple.SE
@TetsuyaYamamoto 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.
@Makyen 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.
@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.
@TetsuyaYamamoto 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.
@TetsuyaYamamoto 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.
@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.
@Makyen - The point being made was that the other user updated the spam to unspam it and save the post, making your comment delatable (as old/noise/no longer needed) instead of making the spammer's post deletable - the opposite of what it seemed that you wanted. --- Leaving it with you, as long as you understand what it is I'm explaining.
@Rob Yep, I understood. I appreciate you pointing me to the post. My next revisit wasn't scheduled until Saturday. This way it was deleted sooner. I agree adding disclosure for the user, based on assumptions from other posts, was inappropriate. If the answer was of good quality and/or had significant value to the question, then I could understand editing in some type of disclosure for the user, but the answer really was low quality and the product was also mentioned in two other answers.
@ArtOfCode - Whom was it here that was writing a program for Winter-bash Knitting? - I have a suggestion, in addition to more colors we have animated knitting.
[ SmokeDetector | MS ] Link following arrow in body, pattern-matching website in body, potentially bad keyword in body, potentially problematic ns configuration in body (197): How to install AOL Desktop Gold? by emily blunt on photo.SE
@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, blacklisted website in body, body starts with title and ends in url, link at end of body, +3 more (593): 800MG Rapid Results Keto by Sandradsosa on superuser.com
tpu- feedback received
[ SmokeDetector | MS ] Url in title, body starts with title and ends in url, link at end of body, link following arrow in body, potentially bad keyword in body, +1 more (393): androstackxblog.wordpress.com/ by deborahevans on meta.SE
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more (491): Vital progenix australia by Alex Tailor on meta.SE
[ SmokeDetector | MS ] Bad keyword in link text in body, bad pattern in url body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body (260): Microsoft Technical Support by outcutlook on drupal.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, +1 more (491): For ideal wellbeing and developme by user973001 on superuser.com
@bertieb 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.
[ SmokeDetector | MS ] Few unique characters in answer, mostly punctuation marks in answer, repeating characters in answer, blacklisted user (300): Cryptic Crossword Hints by Harry Stylesheet on puzzling.SE (@Mithrandir)
