As a very interested lurker, I'm with Julien on this one. There are many reasons why it's good for all of us to have Twitter implement an agreed-upon standard like PubSubHubbub, while there are many good reasons for Twitter to implement using their own proprietary API. Ultimately Twitter using an available standard is better for everyone involved (including them), but in the short run, Twitter has every reason not to use it, and developer solidarity around a standard helps us all.
Jeff On Tue, Mar 2, 2010 at 8:24 AM, Julien Genestoux <[email protected] > wrote: > As I said on the Twitter Dev Group. I think you miss the fact that it's a > "standard" and "inter-operable". It's very counterproductive to have 36 > different APIs for 36 different services. The web is what it is because > people have agreed to build websites with the same standards, which makes it > easy to consume : HTTP, RSS/Atom, email... > > There are also obvious technical advantages, like the fact that you can > actually subscribe and receive notifications at the same time, which is not > the case with the streaming API. > > > > On Tue, Mar 2, 2010 at 8:03 AM, Andrew Badera <[email protected]> wrote: > >> As I said over on twitter-dev ... if streaming gives me everything I >> need, (which it almost does now, and supposedly may do in the future, >> plus commercial considerations may solve my problems) and it's really >> not that complex (which it's not) then why replace it with an >> alternative that doesn't, to me at least, seem to offer any hugely >> distinct advantages? Or, what advantages am I missing? Don't get me >> wrong, I <3 PuSH, but Twitter Streaming is already in place and >> invested in ... >> >> ∞ Andy Badera >> ∞ +1 518-641-1280 Google Voice >> ∞ This email is: [ ] bloggable [x] ask first [ ] private >> ∞ Google me: http://www.google.com/search?q=andrew%20badera >> >> >> >> On Tue, Mar 2, 2010 at 10:58 AM, Julien <[email protected]> >> wrote: >> > Hey, I was expecting a little more debate around that :p >> > >> > After a small day of poll, here are some results : >> > >> > Do you currently use the Twitter Streaming API? >> > Yes 18 53% >> > No 16 47% >> > >> > Would you use a Twitter PubSubHubbub hub if it was available? >> > Yes 33 97% >> > No 1 3% >> > >> > Have you already implemented PubSubHubbub? >> > Yes 24 71% >> > No 10 29% >> > >> > >> > Obviously, 34 is _not_ a big enough number that I think we have a >> > representative panel of respondant, but we also have "big" names in >> > here, (including some who have access in the firehose), which makes me >> > think that PubSubHubbub should be a viable option for Twitter. >> > >> > If you read this, please take some take to respond : >> > >> > http://bit.ly/hub4twitter >> > >> > Thanks all. >> > >> > Cheers, >> > >> > Julien >> > >> > On Mar 1, 3:03 pm, Julien Genestoux <[email protected]> >> > wrote: >> >> Hey all, >> >> >> >> I think everybody agrees that Twitter needs a hubs. We (Superfeedr) >> want to >> >> build it. >> >> >> >> Please help us :http://bit.ly/hub4twitterthe more people in there, the >> >> more comments, the more we can convince Twitter to use ours or even >> host >> >> their own. This has just been wayyyy to long. >> >> >> >> Any comment, question, suggestion and intro is more than welcome. We >> can get >> >> them down this road. >> >> >> >> Julien >> > >> > >
