Oh, I'm not saying that you shouldn't produce content to be the much more common 16:9 format. I just like to be able to view things at 16:9 and still have room for other controls, without having to reduce the width of the content.
Anyone have a sock that can do a bit of science for me? I need a sock that isn't a member of a team. If so, visit stackoverflow.com/questions/tagged/python and tell me if you see the "featured" tab. Then, anyone that is a member of a team (ie. Charcoal) visit the same link and tell me if you see the "featured" tab
stackoverflow.com/c/charcoal/posts/400/timeline doesn't show any change though ... why would someone add a parenthetical to a revision comment? It's not like it's going to be noticed by a lot of people (unless, you know, someone notices and is baffled)
> Bad keyword in title, mostly dots in body, mostly dots in title ---------- Title - Position 1-10: u.c.v.a.v Title - Post contains 4 dots out of 9 characters Post - Post contains 4 dots out of 9 characters
I'm guessing it really wants to apply to a very specific length of pattern (exactly four or five dotted characters) ... and even then, it's unclear what exactly that pattern is supposed to match
a better rule would perhaps be to strip the dots from matches and check against one of the pattern lists, because the TP hits are on stuff like q.u.i.c.k.b.o.o.k.s and f.r.e.e and s.u.p.p.o.r.t
@tripleee That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
[ SmokeDetector ] SmokeDetector started at [rev 9945d3e (tripleee: Add more FP checks for [a-z]\. [a-z]\. [a-z]\. [a-z]\. [a-z] --autopull)](//github.com/Charcoal-SE/SmokeDetector/commit/9945d3e) (running on teward/Solar Flare)
@tripleee Yeah, my problem is that "notification" seems like an unlikely username for someone to have been able to happen to get (i.e. I'd think it in demand). Thus, it's not clear to me if it's a service that's selling it out, or not.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, Pattern-matching website in body, and Pattern-matching website in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@Makyen Blacklisted essaycaptains\.com
CI on 448d1f4 succeeded. Message contains 'autopull', pulling...
Hmmm... we have a watch for \w*essay\w*\.com?, which is at least somewhat redundant with pattern-matching website, but which also gives the impression that we're already specifically watching each essay-writing site which comes through here.
I tend to assign a high probability that if we're watching something as specific as a domain, then it's that we're watching a known specific domain, which we've seen previously. I understand that we can easily watch patterns in domains (I've at least considered setting up a few). What I'd find better is if we had something that was "potentially bad pattern in X" in addition to "potentially bad keyword in X".
I guess part of it is that I use the fact that a domain shows up as watched as a marker that we've seen that specific domain used as spam, particularly when !!/watching a domain.
@tripleee I agree. The only reasonable way to do it would be to have a separate list for watches which are intended as pattern matches to detect things which we haven't actually seen yet. I certainly don't want to be saying people shouldn't use whatever regex capabilities they desire for watches (within reason; e.g. performance considerations).
I've updated Left-sidebar in the Topbar (install) to work with the current version of the left-sidebar. On all SE sites with the left-sidebar, the userscript puts the left-sidebar in the topbar, regardless of the SE site-specific preference you've set.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, body starts with title and ends in URL, link at end of body, +2 more: "I viewed in the air unconfirmed by Wrout197 on askubuntu.com
@SurajRao That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Glorfindel That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
