« first day (395 days earlier)      last day (3428 days later) » 

12:31 AM
@hichris123 Coool
wait a minute, why is Smokey posting "I started" messages?
 
12:46 AM
@Undo shrugs
 
 
3 hours later…
3:44 AM
 
 
1 hour later…
6:41 AM
[ SmokeDetector ] All-caps title: FINDING THE ANSWER by jlucia on physics.stackexchange.com
 
7:08 AM
 
7:58 AM
@hichris123 Yeah, that sounds like a good idea.
@SmokeDetector Hmm... we probably should trim the user name before putting it in a link.
Fixed.
!!/pull
 
...
@Undo Something went wrong when pulling. I think the reason is that you have not committed and pushed when you added the !!/hats and !!/wutDidYouChange commands.
!!/rev?
 
Merge conflicts, probably.
 
[ SmokeDetector ] All-caps title: AN INTERESTING AREAS QUESTION by user160431 on math.stackexchange.com
 
8:08 AM
Oh well, I made a typo in my commit message.
Meh, I'm not going to rewrite history.
 
 
1 hour later…
10:55 AM
[ SmokeDetector ] Bad keyword in title: HowTo thin And Gain Muscle by linda thomas on meta.stackexchange.com
 
 
2 hours later…
12:49 PM
[ SmokeDetector ] All-caps title: H2 ALTER TABLE ADD COLUMN BEFORE/AFTER by dendini on dba.stackexchange.com
 
 
3 hours later…
3:27 PM
You guys may be interested in my post on meta.so
 
@ManishEarth Is there a way to leave a Room in ChatExchange? There is a Room.join() method, but no Room.leave() method.
 
0
Q: Can a machine be taught to flag comments automatically?

AndyTL;DR: Yes it can. Background On June 27, 2014 Skynet awoke. It looked at Stack Overflow and thought "Why are all these people being so chatty and talking about obsolete things? I should nuke them all!" Fortunately, Skynet was a baby and only had access to my 100 comment flags a day. Prior ...

3
 
@Andy You... actually built that? O_o
 
Yeah
 
wow
Great amount of helpful flags!
 
3:31 PM
Thanks.
 
 
1 hour later…
5:28 PM
@Andy wow. That's awesome.
@Andy Any plans to open source it? I think crowd-sourcing the classifier to make it better would be a good option. That's what I always wanted to do with Charcoal, but I never knew what/how...
 
I'll see how the meta post plays out. The SO mods have legitimate concerns about to many of them running. I don't want to overwhelm them with comment flags
 
6:14 PM
@Andy I agree, wouldn't add the flagging part. Just the heuristic -- and probably not announce it anywhere but here.
Also, might want to get Shog's input on this -- he's wanted something like this.
i.e. this:
Feb 4 at 21:00, by Undo
in Tavern on the Meta on Meta Stack Overflow Chat, 20 secs ago, by Shog9
I'm going to be much more open to this if you hand me a list of comment IDs AND document the process by which you accumulated them.
(that conversation)
 
whoa, that's an old conversation. Good memory
 
@Andy Mostly because of this:
Feb 4 at 21:00, by Undo
We have our mission :D
(really, it's what Charcoal should & ought to be. but you did it better. :P)
 
7:02 PM
[ SmokeDetector ] All-caps title: C# DRAW AN ELLIPSES? by gingarr on stackoverflow.com
 
@hichris123 I built a local dashboard because I got sick of messing around the database.
 
woah.
Is this what you've been spending your time on?!?
 
Each of those fields has a break down. So if you wanted to see flagged comments for today:
And you can quickly change either of the dashed underlined fields (type or disputed)
 
ooooh
 
Same with the certainty thresholds
The three that have a 1.0 (and don't flag) I didn't get enough data for that I felt comfortable using, so those haven't been trained against yet
Finally, if I found a comment that I specifically wanted to add to the system, I built that too. Paste the URL to the comment here, classify it and then utilize the API to grab information about it:
 
7:50 PM
wow.
Also, did anyone else notice this?
Hm, thought about doing this with q's & a's yet @Andy?
 
Yes (and no)
 
...
 
Comments are short and sweet. They don't have a lot of content, so it's relatively simple to classify them.
 
True.
I do think that it would work for some cases, though. NAA's seem to have some sort of common text ("didn't work" but not "solved it" "fixed it", etc).
 
I started to build a feature extraction algorithm to see if I could utilize that against one of the quarterly dumps earlier this year.
I had about 20 features I was extracting.
Those ranged from number of code blocks, number of links, spelling errors (which, by the way, will chew through memory if you aren't careful), sentences, question marks, images, links.
Plus the usual up/downvotes, favorites, views and other explicit data provided in a question
The idea was to build a set of features that showed a general "not bad" quality and a "needs to be improved".
Time got in the way. Plus, the quality improvement project seems to be covering most of what I wanted to do anyway
The thing about how I was going about it too, is that the feature set would have to be built for each site. I am not sure if the quality project has a way around that, but since each site gets completely different question types (ie. how often does Earth Science get a question with code blocks?), those specific features may indicate a completely different type of question on another site
If someone wandered into Community Building and posted two or three nicely commented blocks of code and an error message that they are generating, I'd have to say it's off topic. Do the same thing on SO and you've got a good question
 
8:07 PM
Hmm, good point(s).
Regarding links: I've been thinking about finding all links in SO answers, testing if they're broken, and if so it can be another factor in an algorithm. But I dunno.
Something for Winter Break, I guess.
btw @Andy, how long did this take you? Hundreds of hours?
 
Most of the time was spent doing the initial classifications. I had stuff broken into 3 groups, I still went through and made sure that I didn't lump things incorrectly. That's where the majority of the time was spent in the beginning.
The dashboard was build to reduce my time and give me a quick overview. It utilizes Flask and didn't take that long.
Training a new dataset takes a while, but I dump that on the other machine and let it chug along. When the dataset is done, I run it through a few tests to make sure it works as planned.
 
Before I click that link...is that the Data Scientist?
ah ha! :)
I know. I've been considering putting in an app
 
@Andy ... of course not. :P
@Andy Huh, interesting.
@Andy Do it.
 
Time now is spent marking any flags as declined, if I flag something inappropriately (vote here!). That only takes a couple minutes a day.
But, that bit is important so that when I retrain I don't use those comments to train incorrectly
 
 
2 hours later…
10:15 PM
[ SmokeDetector ] Bad keyword in title: Gmail Problem Helpline number 1-855-720-4168 by Neuro Tech on webapps.stackexchange.com
 
11:00 PM
[ SmokeDetector ] Bad keyword in title: Gmail Problem Helpline number 1-855-720-4168 by Mary Smith on apple.stackexchange.com
 
11:47 PM
[ SmokeDetector ] Bad keyword in title: Kaspersky Customer Service Phone Number by johnbotha on webapps.stackexchange.com
 

« first day (395 days earlier)      last day (3428 days later) »