Hi Matt,
We've been seeing this for a while - the block and report spam calls always
return 502s (with a full page of HTML), even though they actually succeed.
This doesn't seem to be tied into the stability of the rest of the API. This
is happening across all of our clients, including those that
Hi TjL,
The API can occasionally return a Twitter Over Capacity error when the site
is experiencing a lot traffic. If this happens waiting a little white and
trying the request again will work.
I notice you are using a variable for the screen_name. Is this being set
correctly in your
I am trying to block users on the command line like this:
twurl -t -d screen_name=$1 /1/blocks/create.xml
I am consistently getting
- HTTP/1.1 502 Bad Gateway\r\n
as a response to this (Twitter Over Capacity) even when it works
(verified via API and via website)
Is this why so few 3rd
