In the guts of OAuth I discover the field oauth_timestamp, for which the specified behavior is apparently that all requests that contain a lower oauth_timestamp value than the highest one ever received should be denied. As I am trying to queue up a number of Twitter API requests for processing, and potentially out-of-generated-order processing for that matter, this nasty little item may really ruin my day.
But, Twitter being Twitter, there is hope: the possibility that they have never actually written code to enforce the specified behavior of oauth_timestamp. Which would be lovely, since I object to it violently.
So, does anybody happen to know whether the Twitter API actually enforces oauth_timestamp's specified behavior?
Twitter restricts oauth_timestamp to be within five minutes on either side of GMT. Outside of that 10 minute window and the requests will fail.