I had similar weird experience on January 8: started to get "incorrect
signature" responses from twitter. Eventually everything started to
work correctly with no code change on my part.
Would be great if there was more info on the subject...
On Dec 21 2009, 9:35 am, jdangerslater wrote:
> Well,
Abraham,
Thank you for your suggestion about "curl http://jazzychad.net/iponly.php";.
Submitting the IP produced by this command seem to have fixed our rate
limit issue.
Thank you,
-Stas
On Dec 13, 8:48 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Depends on on your serv
Thanks Abraham,
Does this mean that the IP produced by "traceroute http://myservername.com";
was an incorrect one?
Thank you,
-Stas
On Dec 11, 12:36 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Make sure you got the correct IP whitelisted.
>
> From your server do
In other words, how would
somebody like HootSuite would approach this? They are getting
thousands of status, screen name, etc. per minute it seems.
I think we are missing something obvious.
Thank you,
-Stas
On Nov 23, 2:56 pm, Michael Steuer wrote:
> Youre seeing rate limit errors for unauth
We have received whitelisting approval from Twitter, but seems it is
applicable to the @name and the IP.
Given that we still get "rate limit" errors, should we just whitelist
the IP?
If so, what is the process of changing the whitelisting options?
Thank you,
-Stas
