@ThomasWard Notes: Currently being heavily abused by someone who is a member of that site's staff on Ask Ubuntu and al they do is post non-answers that link back to that site (of which they 'authored' those answers on the other site). Ask Ubuntu has seen this multiple times and we have issued two suspensions now against the user spreading this as a result of their ongoing spamming of this site's links without attribution to the point it's a violation of the self-promotion and spamming policies.
@ThomasWard So... Yes, you're right, but I'm inclined not to point SD at it because:
1. They're really more link-only answers than classic spam 2. It's a user-generated-content site; we wouldn't blacklist e.g. GitHub if some idiot had a repo they were linking stuff to 3. I do have a soft spot for Codidact in general, as a counterbalance to SE management doing silly stuff.
yeah I use watchlist for temporary things, rather than a blacklist. There's very few times I"ve had to actually blacklist a URL. Watchlist isn't designed I think for permanent blacklisting
@Undo though, stripping the core functionality and blacklists out of Smokey and making it a mod-specific tool that lurks in CHQ with a Metasmoke backend wouldn't hurt, but I don't want to dupe Metasmoke too.
you and I both know how Evil(TM) Metasmoke is to deploy
remind me who designed the SmokeDetector logo
i might want to alter it to be a diamond instead of a flame with a crosshairs on it for modwatcher which we could eventually have as a CHQ side project
but let me get the ton of crap off my FT job work plate first
@Nick custom flag, spam flags are theoretically fine but not every moderator has seen these. BrowserStack has been doing this for a little while now, so we've been mostly treating them as spam (hence the watchlist).
Unfortunately they don't seem to stick to one account or listen when we tell them to knock it off.
It's at least not clearly sockpuppetry either so I assume they've just hired some incompetent vendor or something.
Regrettably, the custom flag queue is a huge mess at the moment due to a large glut of plagiarism being discovered, and the problem that handling it tends to result in finding more...
@Nick Side note: Just in case you're not aware, this has been an issue for quite a while now (that regex isn't watched - it is a combination of a few I've been looking at though)
The quota_remaining property was not in the API response. Error: no method found with this name at 04:18:16 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
Hello! I've finished an alpha version for an updated MS dark mode (as a userscript). Note that a decent amount is unfinished, especially with the text on the charts, and contrast ratios still aren't all full right, and I've also re-arranged part of the UI. If you'd like to test it, you can install it here.
3
I have a few TODOs in the script itself, but if you find an issue that isn't mentioned there already (or something still light themed), leave a comment on this GitHub issue and I'll try to fix it. The URL will of course change once it is released (as it is currently located in my GH fork).
I also use an external library called Less as well. I'm inclined to keep using it, but it is a new library, so I'm not opposed to switching to plain CSS.
TL;DR I have a (working) alpha version of an MS Dark Mode userscript, and bugs/issues/feedback should go here - install link
[ SmokeDetector | MS ] Bad ip for hostname in answer, bad ns for domain in answer, blacklisted website in answer, potentially bad ns for domain in answer (272): Nginx server redirect loop by MargaretSto on stackoverflow.com
@tripleee A normalized version, {{'7815000083'}}, of that pattern is already on the number watchlist and the pattern you provided is not an exact match to an existing entry on the number watchlist. You can use !!/bisect-number 7815-0000-83 to determine which entries on the number lists match that pattern, which would tell you: Matched by 7815000083(?#IS NorAm) on line 3163 of watched_numbers.txt: 7815000083 found normalized
@tripleee That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 781-800-0083 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 781-800-0083. Append -force to the command word(s) if you really want to add the pattern you provided.
