Re:Ask HN: API limitations for Web services
by capablanca on Thursday January 21, 2010 @05:44AM
(#1067022)
I'll take a look at the streaming API.
"You can also get full firehose access if it really does become successful (...)"
Sorry, I don't understand what "firehose access" means in this context. Care to explain? :)
Re:Ask HN: API limitations for Web services
by aditya on Thursday January 21, 2010 @06:05AM
(#1067044)
Re:Ask HN: API limitations for Web services
by biafra on Thursday January 21, 2010 @06:17AM
(#1067063)
Firehose gives you all the tweets in almost realtime. Its the big brother of the gardenhose. Its not publicly available. I would like to know what the conditions are to get it.
Is just asking nicely enough?
Re:Ask HN: API limitations for Web services
by thamer on Thursday January 21, 2010 @07:39AM
(#1067163)
Twitter announced at LeWeb in December that they would open the Firehose to all developers in “early 2010”: http://mashable.com/2009/12/09/twitter-firehose/
A perfect example is the completely under-powered lists feature, the API is super powerful but twitter's implementation is as barebones as it can be, possibly because they want to encourage other people to build on top of their stack.
Have you looked at the Streaming API for your ideas? You can also get full firehose access if it really does become successful. Obviously, sharecropping on someone else's farm is never a brilliant idea but if you're going to do it, Twitter may not be such a bad place to do it...