« first day (361 days earlier)      last day (3463 days later) » 

2:06 AM
Recovered from WebSocketConnectionClosedException
 
2:55 AM
[ SmokeDetector ] Bad keyword in title: Nike Tn Pas Cher Officiel Site,Chaussures TN Requin Soldes by SADASDA on drupal.stackexchange.com
 
3:25 AM
[ SmokeDetector ] All-caps title: REALM.IO SWIFT DELETE 1 OBJECT by zapKILIG on stackoverflow.com
 
3:59 AM
@SmokeDetector false
@SmokeDetector thank you
@SmokeDetector false
 
@ManishEarth Registered as false positive, but could not add the title to the Bayesian doctype 'good'.
 
LOL
 
 
1 hour later…
5:27 AM
[ SmokeDetector ] Bad keyword in title: Muscle Building Wave by ti sion on meta.stackexchange.com
 
5:51 AM
[ SmokeDetector ] Bad keyword in title: Dose Of Truth About Weight Loss Diets by timsyroyed on drupal.stackexchange.com
 
 
2 hours later…
7:31 AM
[ SmokeDetector ] Bad keyword in title: I you'll find on and we tell you exactly MUSCles body by Lois Putnam on drupal.stackexchange.com
 
 
3 hours later…
10:03 AM
[ SmokeDetector ] All-caps title: VENTURE CAPITAL by SUSAN on money.stackexchange.com
 
 
2 hours later…
12:36 PM
[ SmokeDetector ] Bad keyword in title: What is people review for skin care products? by katitetorres on drupal.stackexchange.com
 
 
3 hours later…
3:57 PM
[ SmokeDetector ] Phone number detected: Cannot access memory at address 0x2e2f6c7236323900 by abc on stackoverflow.com
 
4:09 PM
@ManishEarth It registered that? :O
I think the regex doesn't match it so it doesn't actually register that but it still replies that. @Undo Can you please check whether there is something in the falsePositives.txt file that is not a pair of a site and a question ID?
 
@ProgramFOX true
@ProgramFOX true
true
 
hehe, there is a check to avoid SmokeDetector to reply to your messages :P
 
@ProgramFOX true
 
4:38 PM
rofl
@ProgramFOX Am I looking near the top or the bottom?
 
@Undo Hmm... probably bottom, let me check.
 
@Undo true
 
(read: let me abuse my own chatbot to test this out)
 
@ProgramFOX true
 
@ManishEarth Do you want to hand in your moderator diamond and give it to me? :P
 
4:40 PM
@ProgramFOX true
 
Diamonds are non-transferrable, kinda like tickets to football game.
 
@Undo true
 
@Undo Bottom.
 
k
Vislam.stackexchange.com
p77
tp78
a(V77831
p79
Vandroid.stackexchange.com
p80
tp81
a(V43863
p82
Vmagento.stackexchange.com
p83
tp84
a(V26913015
p85
Vstackoverflow.com
p86
tp87
a.
Looks fairly normal to me, but I don't speak Python file storage weirdcode
 
The last item leads to a valid SO question, so it didn't register it, it gave the wrong reply.
@Undo New rev to pull. Now it replies a correct message when fp'ing a non-report.
 
4:53 PM
k :D
@SmokeDetector false
 
@Undo Could not register title as false positive.
 
@SmokeDetector true
 
@Undo Something went wrong when registering title as true positive.
 
:D
 
5:17 PM
@Unihedron, if this was directed at me, I understood that you wanted to create a regex that would be more strict in it's determination of a POSSIBLE phone number, before sending it to the phonenumbers validation check. Correct?
 
@Andy yes
I though you might have misunderstood as me trying to create a super regex for the phone numbers and put an overhaul through the current approach.
 
Initially I did. I think you were saying you wanted to be able to narrow down false positives like 0x2e2f6c7236323900 by checking if the "phone number" part of that is surrounded by other chacters
in this case, the preceeding c would eliminate the check
 
@Andy Well, I can craft the regex such that doesn't eliminate incorrectly.
 
Spiffy
 
 
4 hours later…
8:58 PM
Would that mean that in the case of ELU and its voodoo witchdoctors, a phone number would only need to include an o instead of a zero for it to pass the test?
ELU uses Georgia, with non-lining figures, and 0 and o look very similar.
I'm afraid that as far as I'm concerned, false positives are far preferable to missed positives.
 

« first day (361 days earlier)      last day (3463 days later) »