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.
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.