To see what the status of your IP is regarding rate limit, issue the
following from that IP address:
curl -I http://twitter.com/users/show.xml?screen_name=dougw | grep X-
RateLimit-Limit
If it's well above 150 then you're whitelisted.
On Sep 1, 11:28 pm, Andy Pirate piratea...@gmail.com wrote:
I don't think white-listing is going to help with a latency problem. It
only gets ya way more API GET requests per hour.
Latency issues are probably due to twitter infrastructure problems,
i.e., delays in the back-end DB servers posting updates from the
front-end UI servers. We've been seeing
Well I checked it out, and it says 150 is the rate limit on any random
member, except my actual account is set 2.
Now this seems like it only whitelisted my actual account. I obviously
can't ask all the members to request a whitelist from twitter, that
would thousands upon thousands of
While we occasionally have update latency events (I think there was
one yesterday afternoon for a bit of extra latency over a few tens of
minutes), nearly all updates are applied to nearly timelines within a
few seconds. The common case is even less latency. Some variance can
be expected when a
We've experienced this at random, whether the user has 1+ million
followers or whether they have 20 followers. I generally don't mind if
the post has the timestamp of 15~ minutes past the time we actually
sent the request. As far as the timestamp being posted, that is also
delayed as well.
I can
