-
Website
http://www.louisgray.com/live/ -
Original page
http://blog.louisgray.com/2008/07/twitter-chokes-unauthenticated-api.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
charlieanzman
60 comments · 11 points
-
Jesse Stay
221 comments · 70 points
-
Ari Herzog
43 comments · 21 points
-
ChangeForge | Ken Stewart
133 comments · 18 points
-
drewolanoff
64 comments · 53 points
-
-
Popular Threads
-
FTC Disclosures Made Simple For Bloggers With Conflicts
6 days ago · 46 comments
-
Still Waiting for An Evil Google? It's Not Going to Happen.
6 days ago · 30 comments
-
Fighting Bots With Bots on Twitter, Leveraging SocialToo
1 day ago · 5 comments
-
Simler Adds Likes, Favorite Tags, Revamps Homepage
1 day ago · 4 comments
-
Gowalla Raises $8.4 Million for Location Check-in Service
1 day ago · 2 comments
-
FTC Disclosures Made Simple For Bloggers With Conflicts
Indus
Anyone who builds a service depending on more than a request a minute from a single data stream should realize they're treading on very shaky ground. I have little sympathy. If you were GM, you wouldn't have one and only one brake supplier... having one supplier is just not a good business strategy at all, so these Twitter apps are risky propositions from the start.
Now, witness the power....
dunno
but damn good reporting mr. gray
I guess you should use twitter search api (summize) get public data instead of regular api.
Our side project http://www.tweetmeme.com which was the first twitter URL tracker has now been down for months because we were offered the use of the XMPP feed and by the time we had implemented they pulled it. We will not bring it back up again or put development effort into it unless these kind of restrictions are a thing of the past.
It is a real shame because twitter became strong because of a really simple to use RESTful API that developers flocked to, by restricting access they are cutting off what made it what it is, this can only have a detrimental effect in the long term.
I would happily use the authenticated API if it means that twitter can offer better service to its users and people like me that are using it in ways that twitter did not expect.
Twitter is just coming to a point where they're realizing that they can't easily sustain their previous models. Anyone that is currently using unauthenticated calls will soon be able to pull from Gnip to be able to optimize their calls (and likely, be more accurate than they were before).
APIs are a tough game...both on the consumer and the producer level. Twitter understands that their developers are their lifeblood, that's why they're working hard to improve the service for all. I think it's safe to say that the reason they're bumping up the auth'ed calls, and down the unauth'ed calls is because more people actually interact with services that are authenticated. Think Twhirl, Twitterrific, Socialthing!, etc. Now, the non-authenticated services are probably pulling far more data at a much larger detriment to Twitter, but most of the activity isn't going on with those places. This move is a very positive thing for the API as a whole, and you can rest assured that they will likely have other solutions for folks that simply can't auth the API going forward.
Great post, Louis