April 2013

@rtroncy @LeonDerczynski @ereteog @armandBrahaj @spbail @yprie @vrandezo In the concrete case it’s bit.ly/13IaVip but seen before.

9:51 AM, Apr 30th, 2013 via Echofon in reply to rtroncy

@TimCohn Thanks, happy you like it. I’m working on several improvements, watch this space… Full credits to the amazin#Wikipediaia community!

9:42 AM, Apr 30th, 2013 via Echofon in reply to TimCohn

@StephenSidlo Hi. You can check out the source code & run your own instance. Languages are individually selectable: bit.ly/13I9QqU

9:38 AM, Apr 30th, 2013 via Echofon in reply to StephenSidlo

@BorjaBalle Especially if every journal does that, the (hoped for) effect will neutralize…

12:35 PM, Apr 25th, 2013 via Echofon in reply to BorjaBalle

@GuardianJoanna @guardian Great, will reach out once it’s ready. Cheers.

11:39 AM, Apr 21st, 2013 via Echofon in reply to JoannaG

@GuardianJoanna I’m thinking of creating a Twitter bot that automatically tweets breaking news candidates. Wanna beta-test w/ The @guardian?

9:54 AM, Apr 21st, 2013 via Echofon in reply to JoannaG

@robinson_k Bummer :-( You can give the talk again, @BcnJS is always looking for great talks :-)

2:03 PM, Apr 20th, 2013 via Echofon in reply to robinson_k

@bkeegan I was discussing a near-realtime API for page view logs w/ @dvanliere the other day. I can see synergies :-)

4:26 PM, Apr 19th, 2013 via Echofon in reply to bkeegan

@bkeegan Thanks for this great article. I was wondering if you were interested to team up for the next iteration of Wikipedia Live Monitor?!

4:25 PM, Apr 19th, 2013 via Echofon in reply to bkeegan

@dret @stilkov Does that still qualify as en-US? Or is it rather en-DE?

8:46 PM, Apr 17th, 2013 via Echofon in reply to dret

@francisybea Planned: EDIT classification & categorization to have more precise (& even less error-prone) signals. Also live page VIEW logs.

1:45 PM, Apr 17th, 2013 via Echofon in reply to francisybea

@mhausenblas Thanks :-) On an unrelated note, I’ve just sent you an email…

7:56 AM, Apr 17th, 2013 via Echofon in reply to mhausenblas

@BcnJS I happen to be in Barna on May 2 & am happy to give a talk on breaking news detection w/ #Wikipedia & #nodeJS bit.ly/ZyrglB

12:59 AM, Apr 17th, 2013 via Echofon

@puppetMaster3 @LeaVerou Sure, but you can do things like, e.g., run pixel calculations in an non-appended <canvas> or prepare <form> data.

2:00 PM, Apr 15th, 2013 via Echofon in reply to puppetMaster3

@mparramon English on demand. There is demand tonight :-)

1:11 PM, Apr 15th, 2013 via Echofon in reply to mparramon

@LeaVerou I made similar experiences w/ links (<a>) that you can click() in Chrome w/o appending them to the DOM, but nowhere else.

12:51 AM, Apr 13th, 2013 via Echofon in reply to LeaVerou

@lechatpito LOL, I always used bahn.de while I lived in France. I tried hard to use sncf.fr, but it was just impossible…

11:31 PM, Apr 11th, 2013 via Echofon in reply to lechatpito

@PrimlyStable @PaulMarks12 Think bit.ly/ZovdsS (broke on Twitter). Idea is using Wikipedia to filter social network spurious events

11:20 AM, Apr 11th, 2013 via Echofon

@WikiWatchBlog Idee ist via wohldef. Kriterien (Paper) zu entscheiden, ob zeitnahe Edits am selben Artikelcluster ein News-Event darstellen.

11:10 AM, Apr 11th, 2013 via Echofon in reply to WikiWatchBlog

@hfmuehleisen But, but, does your mouse wheel work? #Troll #Linux

10:57 AM, Apr 9th, 2013 via Echofon in reply to hfmuehleisen

@RubenVerborgh Congratulations! Sounds like it was a tough run by looking at the mailing list archives ;-) #N3 #Turtle #RDF #nodeJS

1:25 AM, Apr 9th, 2013 via Echofon in reply to RubenVerborgh

@rtroncy This was from earlier that day, while he was in Germany: bit.ly/YbtoVb. My depicted micro-event is from his dinner in AMS…

10:13 PM, Apr 8th, 2013 via Twitter Web Client in reply to rtroncy

@stilkov Go fix your Web — (when I grow up, I’ll be an em dash) bit.ly/xkcd37

12:37 PM, Apr 8th, 2013 via Echofon in reply to stilkov

@netlabsorg @nicolastorzec Let’s take this to the proper forum: bit.ly/16HHQ8w has a “Contact Information” section. HTH. >CC: @fbase

11:45 AM, Apr 8th, 2013 via Echofon in reply to linkedktk

@netlabsorg @nicolastorzec Unsure if it is ‘cause “Google didn’t understand that part of RDF”… Your name suggests you speak de-CH: Sachzwang

11:23 AM, Apr 8th, 2013 via Echofon in reply to linkedktk

@nicolastorzec Strong +1 to that. From my experience, you hit the dereferencing issue w/ way smaller datasets already. Fundamental issue…

9:26 AM, Apr 8th, 2013 via Echofon in reply to nicolastorzec

@nattiyak Hi there. Have you guys seen our #RAMSS2013 paper “MJ no more”? arxiv.org/abs/1303.4702 Hope to chat with you at #WWW2013 :-)

10:34 AM, Apr 5th, 2013 via Echofon in reply to tomayac

@abursuc Thanks. I have quality as a ranking factor. In the concrete case, though, it was outweighed by the image’s social signals.

8:06 PM, Apr 4th, 2013 via Echofon in reply to abursuc

@rtroncy Shaky because shot with my iPhone filming my screen :-)

6:16 PM, Apr 4th, 2013 via Echofon in reply to rtroncy

@sympapadopoulos A crawler? Then your base isn’t the Web browser, but whatever language your server speaks… That’s probably a good thing :-)

4:25 PM, Apr 4th, 2013 via Echofon in reply to sympap

@RubenVerborgh Mr. @rtroncy said he’d dig down in his archives to reconstruct the conversations that were had between the CSS & MF WGs.

2:44 PM, Apr 4th, 2013 via Echofon in reply to RubenVerborgh

@RubenVerborgh World-peace would be nice, too… I’m dramatizing, sorry. <video> is actually quite clever w/ just requesting needed parts.

2:41 PM, Apr 4th, 2013 via Echofon in reply to RubenVerborgh

@RubenVerborgh Sure, but as discussed off-Twitter w/ @rtroncy before, there is (close to) no server-side fragment creation. All client-side…

2:37 PM, Apr 4th, 2013 via Echofon in reply to RubenVerborgh

@sympapadopoulos It is. Check bit.ly/V6YTPE bit.ly/RNDh6O. It’s just not as exact as having non-streaming direct access.

2:04 PM, Apr 4th, 2013 via Echofon in reply to sympap

@sympapadopoulos In HTML5 video, you don’t have access to low-level codec-specific things like keyframes. There’s no notion at all about it.

2:00 PM, Apr 4th, 2013 via Echofon in reply to sympap

@sympapadopoulos Wait, are you talking about #HTML5 <video>? Because I am. I have not worked w/ videos in Java, only a bit w/ FFmpeg.

1:52 PM, Apr 4th, 2013 via Echofon in reply to sympap

@sympapadopoulos There is no notion of frames, though, just time (w/o exactness guarantees). For events, check bit.ly/13TTFuH.

1:37 PM, Apr 4th, 2013 via Echofon in reply to sympap

@sympapadopoulos Supposing this is for <video>. Then keyframes no, fragments yes. Just seek to the position and wait for the “seeked” event.

1:35 PM, Apr 4th, 2013 via Echofon in reply to sympap

@mnot For the record: I’d have preferred all to use/extend existing standards à la #DublinCore. But then, there’re proprietary use cases…

1:57 PM, Apr 3rd, 2013 via Echofon in reply to mnot

@mnot Well, I suspect a strong “not invented here” motivation (but I’ve no inside info). Also check bit.ly/10vaWo1.

1:54 PM, Apr 3rd, 2013 via Echofon in reply to mnot

@mnot Re: “proprietary extension to HTML”—To be fair, they’ve edited the MetaExtensions Wikibit.ly/10vaB4Pm (search for “twitter:”).

1:51 PM, Apr 3rd, 2013 via Echofon in reply to mnot

@afterglowlee Thanks :D xywh.js crops, while #smfplayer highlights. Both are valid use cases. @rtroncy knows the full WG discussion history…

10:51 AM, Apr 3rd, 2013 via Echofon in reply to afterglowlee

@jaymyers Had that issue w/ @edsu. It eventually worked, but unsure why (he made a pseudo pull request). I suspect a general @github issue.

10:07 AM, Apr 3rd, 2013 via Echofon in reply to jaymyers

@rtroncy @afterglowlee Hi Yunjia, smfplayer looks cool. Did you see xywh.js? bit.ly/WEegzU This might make your life easier.

11:18 PM, Apr 2nd, 2013 via Echofon in reply to rtroncy

@PFCdgayo Just sent you an email…

11:39 AM, Apr 2nd, 2013 via Echofon in reply to PFCdgayo

@PFCdgayo Wow’ed by the paper’s outcome. This indeed casts shadows on any & all results of streaming API analysis where filters are applied.

11:27 AM, Apr 2nd, 2013 via Echofon in reply to PFCdgayo

@PFCdgayo Aware of applied filters. Yet, sample seems smallish. Let’s assume completeness, tho. Then enormous!! boosting of matching tweets.

11:25 AM, Apr 2nd, 2013 via Echofon in reply to PFCdgayo

@PFCdgayo Also 528592 / 1280344 * 100 ≈ 41%, which is >> 1%, i.e., the supposed relation of streaming vs. firehose. What do I misunderstand?

11:19 AM, Apr 2nd, 2013 via Echofon in reply to PFCdgayo

@PFCdgayo Thanks for sharing. Data collected 2011-12-14—2012-01-10. Only 528592 tweets Streaming; 1280344 Firehose. Understand why so few?

11:13 AM, Apr 2nd, 2013 via Echofon in reply to PFCdgayo

@rtroncy Some 404’ing project icons, vacancies link broken. Besides that, nice update.

12:31 PM, Apr 1st, 2013 via Echofon in reply to rtroncy