OK I get to have """fun""" designing a DSL for this server thing because I just found out SOCVFinder is actually really complicated and does a bunch of queries against this DB it holds
also the template string was kinda looking clunky anyways
So here's what I'd vote: tp for our purposes, because I would have zero issue blocking obvious crackpot things at submission, but accept AJ's decision because (1) he's sane, and (2) it is kinda borderline.
@quartata Knowing only how to spell "Ruby" and nothing else about that language...that seems counterintuitive. It's called "keep". Why would you delete them?
I was gonna try faye anyways. I just had to go through 4 or 5 other libs first :)
But yes, faye works goodly.
I have heard good things about em-websocket (better for concurrency ... or something ... because it runs on EventMachine). If you can make it work, you're a wizard.
Also, if you're working with rails, use actioncable
The driver needs an object that responds_to? :url and responds_to? :write. I just chose to make WSClient the class that does that, because then I've got all the WS logic in one place. docs here
[ 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: Thrustuline Boost by danny harvey on superuser.com (@iBug)
[ SmokeDetector | MS ] Bad keyword with email in answer, pattern-matching email in answer, potentially bad keyword in answer, blacklisted user: Islamic divorce by jessica brown on islam.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, +5 more: getsupplementhelp.com/testro-t3/ by rkm on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, bad keyword in username, blacklisted website in body, +1 more: BioFlex XL Advantages? by BioFlex XL on graphicdesign.SE
@SmokeDetector " helpful - the code is actually from a very old Google Code repository. Certainly not from that cyberforum which you all have flagged." My google-fu needs improvement
@iBug Repairable use of offensive language should be edited out. In fact, the SD feedback guidance explicitly states that such posts should be edited and the feedback should be f.
@iBug No, it's low quality, not VLQ. It's an understandable, actual attempt to answer. VLQ means that it's not something that could be understood to possibly be an answer. This recent meta discusses it. Here are two more: 1, 2.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in URL body, blacklisted website in body, link at end of body, +1 more: Max trim 365 reviews by skeltydetru on meta.SE (@iBug)
Title - Position 23-44: company in coimbatore Body - Position 952-973: company in Coimbatore
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, +1 more: ilus Anti Aging Serum by user271686 on apple.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: healthpluscogni.com/testro-t3/ by chot on askubuntu.com
@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.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-13: indiaeve.com Body - Position 1-13: indiaeve.com Username - Position 1-13: indiaeve.com
The encripted msj is doing trought tweeter and uncripted thrught tweeter, the feed used is XMLNS a commosns one feed.
