@quartata Also, you know that instead of {:a => 'b'} you can do {a: 'b'}, right? I see you doing it the first way in a couple places, and it's just kinda ugly IMO. I believe that rubocop will correct it.
Also, inline if statments, e.g. if <some condition>; puts 'Hi'; end is the same as puts 'Hi' if <some condition>
The colons make sense to me because humans use colons in lists (also JSON) and symbols are prefixed with colons anyways. The rockets are more chars and so are noisier to me. Although, here's a thing I don't like: {"a": "b"} == {:a=>"b"}
@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.
I don't understand why something simpler hasn't been made when all it needs to do at minimum is move some folders around, browserify and glue into one file
problem isn't really the configuration itself, although having to write it in JS is a nuisance
it's this same thing that gulp does, where everything has to have a wrapper plugin around it if you don't want to have to write 10+ lines to run a shell command in a pipeline
also making people use yarn is dum
Whatever happened to Bower anyways, I remember using it for ASP.NET like a year or so ago and it didn't totally suck
[ 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, +2 more: x4up.org/science-based-six-pack by xbsu on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, blacklisted website in body, repeated URL at end of long post: Science Based Six Pack by seaxqeruaz on stackoverflow.com (@iBug @TetsuyaYamamoto)
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +3 more: how Neuactive Serum work? by kellyhill 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, +1 more: x4up.org/science-based-six-pack by xbsu on apple.SE
[ 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, +1 more: Reaction Male Enhancement by rasternicer 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, +3 more: x4up.org/science-based-six-pack/ by pxqupsles on askubuntu.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-25: shardhamanavayurveda.com Body - Position 1-25: shardhamanavayurveda.com Username - Position 1-25: shardhamanavayurveda.com
[ 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: Alpha hard reload by shemriderlet on meta.SE (@iBug @TetsuyaYamamoto)
[ 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: healthflyup.com/thin-from-within/ by uaqu on askubuntu.com
[ SmokeDetector | MS ] URL-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, link at end of body, +1 more: mumybear.com/viabol/ by Janet M. Beatty on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, blacklisted website in body, pattern-matching website in body, repeated URL at end of long post: Thin From Within by Thin From Within on stackoverflow.com (@iBug @TetsuyaYamamoto)
The LQP queue isn't there to handle spam. People that see spam, or automated processes that detect spam, should be casting spam flags, not VLQ flags. The LQP queue is there to handle posts with different types of problems than spam. If you see a post in that queue (or any queue) that has a pro...
[ 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: healthflyup.com/thin-from-within/ by uaqu on apple.SE
[ SmokeDetector | MS ] URL in title, blacklisted website in body, blacklisted website in title, link at end of body, repeated URL at end of long post: mumybear.com/viabol/ by Janet M. Beatty on workplace.SE
[ 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: Neuactive Serum by user272429 on apple.SE
tpu- by John Dvorak
[ 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: Jojoba Sebum For Charming Skin by ouiseparrow on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, link following arrow in body, repeated URL at end of long post: All about Maxx Boost by Goic 19 on drupal.SE
[ 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: Precautions of Testro t3: by Lauch19 00 on graphicdesign.SE
The LQP queue isn't there to handle spam. People that see spam, or automated processes that detect spam, should be casting spam flags, not VLQ flags. The LQP queue is there to handle posts with different types of problems than spam. If you see a post in that queue (or any queue) that has a pro...
