Just to close the loop on my issue: I got some off-list help, Twitter
investigated, and it turns out my IP address had been blacklisted in
error. The blacklisting is removed, and I'm back in business.
I must say it's nice that I could ask a question on this list, and get
pretty much immediate
John:
Thanks very much for the reply.
On Nov 14, 8:30 pm, John Kalucki jkalu...@gmail.com wrote:
This sounds like you were ignoring HTTP error codes and eventually got
blacklisted.
Consider:http://apiwiki.twitter.com/Streaming-API-Documentation#Connecting
Hmm... I was launching single curl
I had the same issue. And i was blacklisted.
On 11/15/09, Jim DeLaHunt jim.delah...@gmail.com wrote:
John:
Thanks very much for the reply.
On Nov 14, 8:30 pm, John Kalucki jkalu...@gmail.com wrote:
This sounds like you were ignoring HTTP error codes and eventually got
blacklisted.
There are two levels of blacklisting. One is a temporary band that
resets every few minutes. This one gives you 401 errors. Then there's
an IP black hole that is removed by an operator. Currently the IP
black hole sends a TCP RST, but we might might also null route you.
You can verify an IP block
This sounds like you were ignoring HTTP error codes and eventually got
blacklisted. Consider:
http://apiwiki.twitter.com/Streaming-API-Documentation#Connecting
You can tell for sure by turning off --silent and using -v to see
what's going on. You should be getting some sort of message back, or
