@raffi has a detailed post on the problems with the error codes returned by the Twitter API to report rate limit errors and possible changes to them. This is interesting for a number of reasons:
- If his post is taken at face value, it means that he has a lot of latitude to make some serious changes to the behavior of the API.
- I’m assuming that somebody will eventually have to approve these changes, but Raffi makes no mention of any design meetings or internal debate taking place. It is as if he is discussing code that is totally under his control.
- The response codes that are buried within multiple control structures of any script that interacts with the API are subject to change.
