uh - how are we not opening up our API?

On Sun, Mar 7, 2010 at 6:54 PM, Jesse Stay <jesses...@gmail.com> wrote:

> Why doesn't Twitter just open up their API and patent and then the Twitter
> API becomes "the standard"?  We all change less code that way. :-)  I like
> all these open standards, but it would be so much easier if we could just
> use the existing APIs as standards that we've already integrated into all
> our code.  I think Twitter's losing out on a huge opportunity here by not
> opening up their API.
>
> Jesse
>
>
> On Tue, Mar 2, 2010 at 8:57 AM, Julien <julien.genest...@gmail.com> wrote:
>
>> Andrew, it's not so much about making a "simpler" API, but making it
>> standard : having the same API to get content from 6A blogs, Tumblr's
>> blogs, media sites, social networks... is much easier than
>> implementing one for each service out there.
>>
>> 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, 9:02 pm, Andrew Badera <and...@badera.us> wrote:
>> > But how much simpler does it need to be? The streaming API is dead
>> > simple. I implemented what seems to be a full client with delete,
>> > limit and backoff in parts of two working days. Honestly I think it
>> > took me longer to write a working PubSubHubbub subscriber client than
>> > it did a Twitter Streaming API client.
>> >
>> > It would be nice if the world was full of free data and universal
>> > standards, but if it ain't broke, and it's already invested in, why
>> > fix it?
>> >
>> > ∞ 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 Mon, Mar 1, 2010 at 8:44 PM, Julien <julien.genest...@gmail.com>
>> wrote:
>> > > Ed,
>> >
>> > > On Mar 1, 5:23 pm, "M. Edward (Ed) Borasky" <zzn...@gmail.com> wrote:
>> > >> In light of today's announcement, I'm not sure what the benefits of a
>> > >> "middleman" would be.
>> >
>> > >>http://blog.twitter.com/2010/03/enabling-rush-of-innovation.html
>> >
>> > >> Can you clarify
>> >
>> > >> a. How much it would cost me to get Twitter data from you via
>> > >> PubSubHubbub vs. getting the feeds directly from Twitter?
>> > > Free, obviously... as with the use of any hub we host!
>> >
>> > >> b. What benefits there are to acquiring Twitter data via PubSubHubbub
>> > >> over direct access?
>> > > Much simpler to deal with than a specific streaming Twitter API,
>> > > specifically if your app has already implemented the protocol for
>> > > Identica, Buzz, Tumblr, sixapart, posterous, google reader... it's all
>> > > about "standards".
>> >
>> > >> On Mar 1, 3:08 pm, Julien <julien.genest...@gmail.com> wrote:
>> >
>> > >> > Ola!
>> >
>> > >> > I know this s some kind of recurring topic for this mailing list. I
>> > >> > know all the heat around it, but I think that Twitter's new
>> strategy
>> > >> > concerning their firehose is a good occasion to push them to
>> implement
>> > >> > the PubSubHubbub protocol.
>> >
>> > >> > Superfeedr makes RSS feeds realtime. We host hubs for several big
>> > >> > publishers, including Tumblr, Posterous, HuffingtonPost, Gawker and
>> > >> > several others.
>> >
>> > >> > We want to make one for Twitter. Help us assessing the need and
>> > >> > convince Twitter they need one (hosted by us or even them, if
>> they'd
>> > >> > rather go down that route) :
>> >
>> > >> >http://bit.ly/hub4twitter
>> >
>> > >> > Any comment/suggestion is more than welcome.
>>
>
>


-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Reply via email to