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 party apps can successfully block? Because the
API gives bad information? I've had to follow every blocks/create with
a blocks/exists to see if it really worked or not.


Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to