I'm using the streaming API /track function. The tweets coming in
right now are delayed about 20 minutes (i.e. if I go to the tweet
permalink the moment I get a tweet, it says 22 minutes ago, etc).
Is this an effect of Track Limiting (http://apiwiki.twitter.com/
The Twitter OAuth login is working about 50% of the time for us.
Sometimes we get failures making the initial request for a token. If
that works, and the user gets to the Decline/Accept screen, when they
click Accept the connection often times out before they get a
response.
1. I'm finding that OAuth breaks for periods, then works for periods
(not 1/6 requests, more like works 6 times, then breaks 6 times). When
it doesn't work in Safari, if I dump my twitter.com cookies it usually
works the next try.
I may be the only one to be this stupid, but when I looked at my POST
request functions, I was appending some parameters like Source, etc.
that were common to all requests. But since they weren't there when
the signature was generated, we were getting 401 errors as of 7/27.
Removing those fixed
