@ArtOfCode @Undo @tripleee @angussidney @Andy May be you missed my request yeaterday: Can you please add me to the list of privileged SD users again? I suppose that removal was just accidentially due to a github hicckup. If that was intended just let me know.
Yep. We used to have a system that did this automatically, but didn't need it for a while and it got refactored out. Now it's just a query someone runs occasionally
@πάνταῥεῖ That's... a good question. @ArtOfCode @Andy thoughts?
It's such a rarely used thing that we don't really have procedures for any of this
@πάνταῥεῖ Spam flagging and SD feedback aren't the same thing. They're broadly similar, but there are differences that mean you can be good at one without also being good at the other.
@πάνταῥεῖ That's a good start. What it needs now is for people to agree that you know what you're doing. Probably the best way to do that is to respond in chat to Smokey reports as you normally would - that'll create a record of what you would have fed back, which is something people can look at to tell if you're getting it right
@Undo In the last 1/2 hour, or so, I've gotten quite a few timeouts from MS API requests (issue could be on my end). I also just got a "MySQL client is not connected" error when trying to load the search page (definitely an issue on MS). This is consistent with progressively worse issues which I've seen other times when MS has later gotten locked-up. MS may be getting closer to the point where we've seen lockup.
I believe my primary problem is to give k responses for posts which will be not considered spam. E.g. for linked blogs and such stuff. I got a bit more aware recently, and I have to admit I am quite annoyed seeing such stuff at SO and tend to do the easy judgement (instead of using NAA or VLQ flags and SD responses).
Lemme float something out there for the regex wizards among us: Hypothetically, are you interested in playing with a dataset of classified "want to see" or "don't want to see" HNQ titles from IPS? Would be neat to get a regex or something that can solve that problem.
@iBug @Henders @ArtOfCode @angussidney It looks like MS problems resulted in each of your SD instances going non-responsive (at least wrt. status pings on MS). You each may need to kick your instance.
[ SmokeDetector | MS ] Bad keyword in answer, bad pattern in url answer, pattern-matching website in answer, phone number detected in answer, potentially bad keyword in answer (331): Cargar valores en combobox anidados JAVA by user104125 on es.stackoverflow.com
@Makyen The posts were probably deleted, and it probably wasn't reported because they thought it was isolated incidents and not an overall pattern. It seemed extremely suspicious to me that a user with four overall accounts would post something like that.
@thesecretmaster You run into SSL_connect returned=1 errno=0 state=error: certificate verify failed (unable to get local issuer certificate) on /oauth/return before?
@gparyani have you actually seen any evidence of past trolling?
@EriktheOutgolfer Given that the number detector A) includes the +, even when matching just numbers (according to iBug; I haven't looked at the code), and B) the 1 is usually, or at least commonly, not written with US numbers and there's no way to tell the number detector that a number is optional, then, yes, I feel that adding both forms is needed.
Actually, you really should have 3 entries: +1-888-370-1999, 1-888-370-1999 and 888-370-1999.
> Numbers-only title, phone number detected in body, phone number detected in title ---------- Title - Phone number: 18883701999 Title - Position 0-15: +1-888-370-1999 Body - Position 1-15: 1-888-370-1999
@Makyen 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.
> Numbers-only title, phone number detected in body, phone number detected in title ---------- Title - Phone number: 18883701999 Title - Position 0-15: +1-888-370-1999 Body - Position 1-15: 1-888-370-1999
> Bad phone number in body, bad phone number in title, phone number detected in body, phone number detected in title, potentially bad keyword in body, potentially bad keyword in title ---------- Title - +1-888-370-1999 found verbatim Title - +1-888-370-1999 found verbatim Title - Phone number: 00 18883701999 Body - +1-888-370-1999 found verbatim Body - +1-888-370-1999 found verbatim Body - Position 5-19: 1-888-370-1999
> Phone number detected in title, potentially bad keyword in body, potentially bad keyword in title ---------- Title - 18883701999 found normalized Title - Phone number: 00 18883701999 Body - 18883701999 found normalized
> Phone number detected in title, potentially bad keyword in body, potentially bad keyword in title ---------- Title - 18883701999 found normalized Title - Phone number: 00 18883701999 Body - 18883701999 found normalized
> Phone number detected in title, potentially bad keyword in body, potentially bad keyword in title ---------- Title - 18883701999 found normalized Title - Phone number: 00 18883701999 Body - 18883701999 found normalized
> Phone number detected in title, potentially bad keyword in body, potentially bad keyword in title ---------- Title - 18883701999 found normalized Title - Phone number: 00 18883701999 Body - 18883701999 found normalized
@ArtOfCode well i'm in #ubuntu-hardened on IRC so short of you changing an SSL lib or installing a PPA or something else busted, no ideas about why it's broken :|
