[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +3 more (589): Keto Fit thoughts is aerobic exercising by kddd on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, link following arrow in body, +3 more (688): What is Ketotrin? by Kettrinaus on meta.SE
[ 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, +3 more (590): How To Use Extenze To Desire by Polkieset on askubuntu.com
[ SmokeDetector | MS ] Url in title, pattern-matching website in body, pattern-matching website in title, potentially bad keyword in body, potentially bad keyword in title (295): listofdiet.com/zydenafil/ by Hjecfv256 on academia.SE
tpu- feedback received
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, +2 more (492): Maximum Power XL Buy Now by user1030681 on askubuntu.com
@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.
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body, +1 more (297): There is no side effect of using Testo 247 Canada by gbcverk on puzzling.SE
[ 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, +5 more (592): Boost Xtra Male Enhancement by caradopk on graphicdesign.SE
@double-beep We could, but it's working. :-) OTOH, it's not clear how we're going to resolve GraphiQL long term, given what appears to be a lack of maintenance for the graphiql-rails gem we're using. In addition, I haven't looked at the change log for newer versions of the gem, so I' unsure what we're missing out on by using this older version, or if it's needed/desirable to figure out how to use a newer version.
@double-beep I seems to work for me (i.e. the page loads). Admittedly, I haven't actually tried a query, as the query I'd identified as what I plan to use requires capabilities that interface doesn't appear to have available.
OK. Tried it. It worked OK for a query I'd previously used for testing.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +4 more (560): Full Spectrum CBD Oil? by brendaarold on askubuntu.com
@tripleee It should be significantly more efficient, if you're trying to get more information than is provided by a single one of the other API routes. For example, in FIRE, it can replace up to between 401 to 500 separate MS API calls with a single call to the GraphQL endpoint, when getting data for all the posts on a page. Actual reduction might be as low as 5 down to 1, if some of the optimizations it makes possible are not implemented.
that's nice but my use case was more along the lines of "maybe this will allow me to do things which are tortured in SQL" but I don't remember the specifics
Googling for the odd alleged name for the show brings up several spam posts with identical content, and nothing else. Flagging as spam. — tripleee8 secs ago
@tripleee 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 keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +9 more (793): orderfitness.org/keto-pro-avis/ by BruLowe on askubuntu.com
@double-beep there's a lot of overlap there, "offensive" overlaps with "potentially bad". I guess the "potentially bad" reasons should be tightened up to not overlap?
@EliahKagan 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, body starts with title and ends in url, link at end of body, +3 more (493): Evianne Cream UK by Thomdriguez on superuser.com
