@micsthepick 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.
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, blacklisted website in body, +5 more: newsupplements2017.com/erx-pro/ by cpnt on askubuntu.com
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +4 more: newsupplements2017.com/erx-pro/ by pekkanupso on askubuntu.com
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +3 more: newsupplements2017.com/erx-pro/ by cpnt on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in URL body, link at end of body, pattern-matching website in body: Testro t3 reviews by jecckychen on meta.SE
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, +1 more: newsupplements2017.com/erx-pro/ by layla hickle on astronomy.SE
[:42149266] That message is not a report. [:42149262] <processed without return value> [:42149218] That message is not a report. [:42149210] <processed without return value>
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +4 more: healthflyup.com/primal-xl/ by vuht on apple.SE
I once worked on a project that was developed by some another developer not from my organization. That developer had saved dates in that format without any separator just for comparison purposes. ;)
Idea @quartata: what if the front end was written in React? You could serve the API from api.whatever, and have a small Lambda (or GitHub Pages repo) on whatever that serves a small HTML page and a JS bundle, meaning that the Rails app wouldn’t have to do as much rendering, and users wouldn’t have to wait for every query to complete before using the page.
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-10: Forskolin Body - Position 1-10: Forskolin Username - Position 1-10: Forskolin
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in title, link at end of body, pattern-matching website in body: Testo Sup Xtreme by JerryPalmore on security.SE
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +6 more: supplementlab.org/primal-growth/ by gqm on askubuntu.com
> Would not be caught as a post, title or username.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, repeated URL at end of long post: HOW TO BUY? hoe hrdjkjk by Marge1213 on workplace.SE