November 21st, 2014

@gklyne @wsREST Maybe you get inspired once you see our CfP :-) We can’t do much about the travel budget, besides maybe VC you in…

8:51 PM, Nov 21st, 2014 via Echofon in reply to gklyne

@IgorBrigadir Guess why our paper is called “MJ no more…”arxiv.org/abs/1303.4702aD). Full text search for “shoulders” :-@milesosbornene

3:58 PM, Nov 21st, 2014 via Echofon in reply to IgorBrigadir

@gklyne Judging from your REST tweet spree, you might be interested in submitting to @wsREST :-)

3:54 PM, Nov 21st, 2014 via Echofon in reply to gklyne

@edsu Right. For the time being, one can <del>at best</del><ins>simply</ins> roll ones own instance of Wikipedia Live Monitor ;-)

3:51 PM, Nov 21st, 2014 via Echofon in reply to edsu

@IgorBrigadir @edsu Fair enough, but no history (no std. deviation) for “just now” created breaking news articles… But works for many cases.

3:40 PM, Nov 21st, 2014 via Echofon in reply to IgorBrigadir

@IgorBrigadir @karpathy @edsu LOL, mostly this. Initially required >1 languages, but now ≥1. Also had ≥2 concurrent editors, now ≥3.

3:37 PM, Nov 21st, 2014 via Echofon in reply to IgorBrigadir

@edsu For text-only: https://t.co/FiewfKYFTc. For media galleries: https://t.co/RssL1LfBmj. Hi callback hell ;-)

3:33 PM, Nov 21st, 2014 via Echofon

@edsu Fully agree. Human in the loop makes total sense, also common “stop hashtags”, like stop words now. Internationally for all languages.

3:30 PM, Nov 21st, 2014 via Echofon in reply to edsu

@edsu (In no way saying current settings’re perfect.) Long-term, article analysis needed & better understanding of article creation process.

3:29 PM, Nov 21st, 2014 via Echofon in reply to edsu

@edsu Getting these thresholds “right” is incredibly hard. Also very much a matter of taste and how “breaking” you require the news to be.

3:24 PM, Nov 21st, 2014 via Echofon in reply to edsu

@edsu Yes. Also surprised, but breaking news conditions (see paper or settings in app) weren’t fulfilled. Mostly ≥3 concurrent editors one.

3:23 PM, Nov 21st, 2014 via Echofon in reply to edsu

@netlabsorg @RubenVerborgh Ironing out some issues later today w/ Ruben, but watch this space for updates ;-)

9:02 AM, Nov 21st, 2014 via Echofon in reply to linkedktk

@edsu Probably a lot of noise, think of hashtags like #RIP. Worth playing around w/, though, interesting idea! Looking forward to code :-)

1:37 AM, Nov 21st, 2014 via Echofon in reply to edsu

@remagio I can offer http://t.co/u19tbu96L3 and http://t.co/H0md0UvUaD. Somewhat related http://t.co/Ko1acRvJQc. Cheers.

1:34 AM, Nov 21st, 2014 via Echofon

@edsu Possible: let @WikiLiveMon detect breaking news, extract hashtags from rel. microposts (based on article titles), follow $TWTR stream.

1:30 AM, Nov 21st, 2014 via Echofon in reply to edsu

@lbjay @edsu People who like @WikiLiveMon also tend to like @mediagalleries ;-) First described here arxiv.org/abs/1403.4289.

1:26 AM, Nov 21st, 2014 via Echofon in reply to lbjay

@remagio @edsu Sure, you can simply adapt https://t.co/nhj2oivo11 to make @WikiLiveMon cover only part of the Wikiverse.

1:24 AM, Nov 21st, 2014 via Echofon

@edsu @lbjay You could adapt the “email” function (link last tweet) & extract hashtags from found microposts; then archive to DB (or email).

1:20 AM, Nov 21st, 2014 via Echofon in reply to edsu

@lbjay @edsu Not sure I fully follow, but @WikiLiveMon already lets you archive posts related to detected events: https://t.co/VWsixnH6dD

1:18 AM, Nov 21st, 2014 via Echofon