Would anyone use a frontend to SmokeDetector/MS that made it kind of more like SO's review queues? (separate queues for new posts, old posts without feedback, new domains, buttons for flagging and feedback and blacklisting...)
For actually viewing the current blacklist I think a purely frontend webapp would suffice. I was building one for blackhole that would fetch the full blacklist the first time it ran and compress it into localStorage then fetch and resolve deltas after that
plus whatever other things I think are useful I guess
kind of aggregating the various SmokeDetector blacklisting commands, FIRE, Metasmoke and Halflife
@quartata Not entirely on board with an extra framework without understanding it first... run me through what it does for us that jQuery alone can't do (or makes difficult)?
The biggest draws for me are the easily reusable views and the observables -- when you change a value in the viewmodel the view updates with it
I can't see what youre replying to but this isn't a part of Metasmoke by the way
If you were talking about adding the blacklist requests I'm not using Knockout for that
This is just a frontend webapp I think might be useful. I'm personally not a fan of managing userscripts so I thought it might be nice to make one app that does these things outside of chat
How to reset the token in Firefox: 1. Open dev tools with a question page open 2. Run `xdLocalStorage.removeItem("fdsc_msWriteToken")` in the console 3. When you flag a new post, it should propmt you for a new token
@Catija I'll take a proper look at your problem when I get back home from holidays on Monday. Btw, yes you will need cookies enabled, I don't think it's something to do with the application itself but rather one of the script's dependencies
[ 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: For effective results take this by joshuajoh on superuser.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: sufficient care of her? by hgagncemg on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: By by the presage mentioned, by Dighs ave on drupal.SE
@NVZ It fits the profile. Always a new user account with no posts, no name, holocaust tag, posting something vague about the holocaust ("zyklon" comes up often).
@NVZ that wouldn't help. Our biggest spammer group (and I assume the majority of the others do this too) has their human workers register an account and then either manually type out or copy-paste some text into a question and then submit it. They get paid when they show some sort of proof that they posted it (we assume a screenshot). Anyway, forcing registration wouldn't do anything because it's humans, not bots, doing the spamming already.
probably trying to actually sell there health products? Actually, that's what they do. You wouldn't believe how many people think it's a good idea to buy pharma pills from a dodgy website.
@Glorfindel That pattern looks like it's already caught by Bad ns for domain in answer and Bad ns for domain in body; use !!/watch-force if you really want to do that.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad keyword in body, +2 more: Neuro Max is works? by petasdas on graphicdesign.SE
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, blacklisted website in body, +4 more: supplement4help.com/dsn-code-black/ by purove on graphicdesign.SE
[ 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: www.7supplements.org/clarityx/ by exced on graphicdesign.SE
Today's IP nightmare: The scripts are a computer-generated work. Law contradicts itself on whether that's eligible for copyright or not; the only relevant case law suggests that the authors of the algorithms that generated it are the copyright holders. However, it's generated based on a set of other smaller works by multiple different people - volunteers - where, in theory, each volunteer holds the copyright to their own work, and the program authors may or may not be able to claim copyright based on the threshold of originality. _But_, those smaller works are also composed of snippets of i…
