[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, link at end of body, +3 more (683): Why Should I Buy Genbrain? by Genbranuk on meta.SE
@Makyen 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 ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +3 more (590): Vital Keto Diet France by galdplrt on graphicdesign.SE
[ SmokeDetector | MS ] Mostly non-latin answer, potentially bad keyword in answer, username similar to website in answer, blacklisted user (181): Baaghi 3 full movie by Money Makar on sports.SE
@Makyen 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.
@Makyen 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.
@Makyen That pattern looks like it's already caught by Bad ns for domain in body and Bad ns for domain in answer; append -force if you really want to do that.
@Makyen 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.
@Makyen 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.
@Makyen 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 ] Url-only title, bad ip for hostname in body, bad ip for hostname in title, bad keyword in body, bad keyword in title, +7 more (989): lionsupp.com/next-form-keto/ by NicolKelley on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, potentially bad ip for hostname in body, +2 more (395): How Does Genbrain Work? by genbrainfr9 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted website in answer, pattern-matching website in answer, potentially bad ip for hostname in answer, potentially bad keyword in answer, +1 more (261): Health Insurance question by samtkinson on math.SE
@SmokeDetector naa- This edit was rightly rolled back, but the intent here appears to have been to improve the post. The post author replaced the text of the post with a link to an image in which formulas are properly rendered. What they should instead have done was to surround each formula by $$ or $$$$ (depending on whether they want it inline or on its own line) so MathJax would render it (and presumably also finish writing the answer: compared to the image, they left out the last part).
@SmokeDetector tpu- This user and the OP have the same email-hash-style avatar, strongly suggesting this is an undisclosed sockpuppet of the OP. It looks like the accounts are deliberately interacting to promote the site linked to in this answer. Other explanations, such as this being accidental and the OP intending to post a self-answer, are imaginably possible. But this still looks like spam, and both accounts are registered and have existed for a while, on multiple SE sites. I raised a mod flag.
@SmokeDetector The site has a number of hits across SO. Although this still strongly looks like sockpuppetry, I don't think all or most of the users linking to it are sockpuppets. I was going to watch the domain and !!/report the question itself as a spam seed; for now I'll hold off on both. I've retracted my mod flag and raised a new mod flag that incorporates this information.
@EliahKagan That pattern looks like it's already caught by Bad keyword in answer, Potentially bad keyword in answer, Bad keyword in body, and Potentially bad keyword in body; append -force if you really want to do that.
Matched by the following regexes: puri[\W_]*+hair(?!(?<=purihair)101\.hatenablog\.com)(?:[\W_]*+(?:\d++|[\da-f]{4,}))* on line 2138 of bad_keywords.txt purihair147\.blogspot on line 17898 of watched_keywords.txt
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, potentially bad ns for domain in body, +1 more (394): Alpha Testo Boost X by Jasonail on superuser.com
@SmokeDetector I'm not sure about this one. Even though the post is recent, the linked page doesn't currently show a "privacy helmet," and it feels like the goal of the post may be to promote the site... but there is an article about that on the site.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +4 more (690): What Is Alpha Titan Testo Canada? by joanterters on askubuntu.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ip for hostname in title, blacklisted website in body, blacklisted website in title, link at end of body, +5 more (795): buyonlinecare.com/formax lean/ by lisvonzuns on drupal.SE
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +2 more (692): top10guider.com/sf180-brain/ by zentorexx6 on askubuntu.com
I gave naa feedback on that post (as I recall, it was already deleted, or I would've submitted an edit to expand it). But I'd consider it to be on the border between fp and naa, rather than between naa and tp.
^^ It's spammily worded, but I think it's probably not spam. The post author has significant non-spam contributions on two SE sites. The contact information in their profile does not appear to match anything on the page on on the contact info on the linked blog. I figured I'd check if Smokey picks up anything on it though.
@EliahKagan 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.
(Of the many hits in MS, 3 from a couple months ago are under the default autoflagging threshold, and there are no false positives in MS or SE search.)
@EliahKagan 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.