@Daniil Yes I'm interested in testing, but I'd want to push a current version of the script prior to anything happening. I did get a version of what the (sanitized) top-bar HTML looked like for two mod items which were at that time in the top-bar, but that was quite a while ago now. The current version of the script should be working with the mod-tools, but I, obviously, don't have a way of actually testing.
While I've continued to work on that script, and use it myself daily, there were just so many changes from SE, that I allowed support to fall behind.
Note: I don't want anyone to be giving me info which I shouldn't have, so testing what I do have would probably be a first step.
user435118
Ok, my favourite script of use is ROOMBA forecaster - I like it a lot
I'll move up the priority of getting the current Top Nav Choices script to the point where it's reasonable to push it. However, it's still below things like actually reviewing the current SD PRs.
[ SmokeDetector | MS ] Bad keyword in answer, bad keyword in link text in answer, pattern-matching website in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, +1 more (248): Commenting (out) code in Angular2 TypeScript by siyaram yadav on stackoverflow.com
@Machavity In general, when you are wanting to watch text that is also used as a domain name, it's preferable to use two watchlist entries, rather than one. One for the domain (e.g. bimedis\.com) and one for the text, with the domain excluded (e.g. bimedis(?!\.com)). The reason for having two is that, assuming they keep showing up in spam, they will eventually be moved to the blacklists, which are separated into the keyword blacklist and website blacklist.
If there are separate entries in the watchlist, it's trivial to blacklist one with just a !!/blacklist-* command, while, perhaps, the other doesn't yet qualify for the blacklist. If there's only one entry in the watchlist, then whoever is moving one or both to the blacklist has to either edit the watchlist to only be the one not being moved to the blacklist, or if moving both, manually !!/unwatch the entry that covers both.
@tripleee 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.
@Daniil there are test cases we run on each commit, sometimes they fail because there is a problem in the code but sometimes it's just something transient on CircleCI
[ SmokeDetector | MS ] Few unique characters in answer, no whitespace in answer, potentially bad keyword in answer, repeating characters in answer (264): Laravel Passport VS JWT by aaaaaaaaa on stackoverflow.com
offshoreclippingpath.com is probably the one I was thinking of but it's actually just 8/8, last seen 3 months ago (all by a user named "Shelley Morris") metasmoke.erwaysoftware.com/domains/47653
> Bad ns for domain in body, bad ns for domain in title ---------- Bad ns for domain in body - techismart.in NS suspicious ns1.sg7.fcomet.com.,ns2.sg7.fcomet.com. Bad ns for domain in title - techismart.in NS suspicious ns1.sg7.fcomet.com.,ns2.sg7.fcomet.com.
