[u...@cl-t090-563cl twitter]$ curl --basic --user UserName:Password -d screen_name=SpammerJane http://twitter.com/blocks/create.xml ... <span style="font-size:1.8em; font-weight:bold">Something is technically wrong.</span><br /> <div style="font-size:1.2em;margin-top: 2px;color:#b6b6a3">Thanks for noticing—we're going to fix it up and have things back to normal soon.</div> ...
I'm building a library of curl calls for use with the CRM114 filter language (as in Spam filtering). It appears that this syntax should be expected to succeed, but fails due to a transient error. I would like to know whether my assessment of that is correct and, if so, how transient. Some volatility is expected with the API under active development. If this syntax is preferred, 'curl --basic --user UserName:Password -d "" http://twitter.com/blocks/create/SpammerJane.xml' (which worked) then I can refactor my code to use the preferred syntax. Alternatively, I can build the library with redundant API calls if warranted. A retry mechanism is probably in order once working calls are in place. What would you recommend for a retry interval? My first thought is to start at 10 seconds and double it each attempt for four days. On a related note, what does a call to the Create Block API return if the user being blocked no longer exists? Chris Babcock
