Here's the typical errors. Call 1 says 132 hits remaining; call 2
returns over the limit. Once an hour, call 2 slips through and returns
the right result. Otherwise, on some accounts - the rate_limit bug
blocks access. On other accounts, there is no problem at all.
Sometimes, the problem resolves
Our IP: 69.107.71.66 Your IP: 168.143.162.68 Via AT&T Dynamic DSL
We host Twitter accounts for enterprise clients - each via basic
authentication 24x7 via FF3.5. No memory leak observed on FF3.5 -
despite the problems. We're staring at dozens of identical Vista
machines - some work happily, other
To help find your external IP, I've setup
http://jazzychad.net/ip.php
(basically a noiseless whatismyip.com)
Or if you want to get only your external IP from the command line, try:
curl http://jazzychad.com/ipecho.php
-Chad
On Mon, Aug 17, 2009 at 8:01 PM, Chad Etzel wrote:
> Hi all,
>
> I'd ju
Hi all,
I'd just like to add that if you can also provide HTTP
request/response headers and/or packet captures/dumps of actual API
requests, that would be really really helpful in troubleshooting
specific situations. Any patterns we can see emerging from this data
will help us debug even faster.
