Hacker News Reader

Well, at least they're giving us a long lead time until 1.1.

Really? 6 month from turning it on to disabling 1.0 is really not that long a time at all. In that time, every client needs to migrate to 1.1 and QA that, and then all the distribution channels (distros, app stores, etc.) all need to get updated versions, and then users all need to upgrade. 6 months is extremely optimistic for that to all happen.

But there's not much change. For most developers it will require no more changes than replacing "api.twitter.com/1" with "api.twitter.com/11" (or whatever it is) and testing a little bit for the new rate limits (which, as Twitter says, will be enough for apps that are currently within those limits).

The bigger problem is for apps than don't authenticate: Search apps, analytics... anything that does not write to Twitter is probably not authenticated. They'll have to migrate to OAuth and requiring user authorization.

But, as I said, this will not be the case for most of apps. Anyways, it wouldn't be bad that Twitter gave more margin to developers.

Reply on news.ycombinator.com