Apparently Twitter is no longer returning a response when a post is sent in using the API – at least according to Craig’s tweet. This is probably designed to help Twitter with their scaling problems, but I cringed a little inside when I read that, because it also breaks a whole lot of Twitter clients that rely on that response to know when a post is successfully sent. I especially feel sad for my iPhone-developing brethren – don’t think I can publicly talk about the details, but I think this means a lot of Twitter clients launching on the iPhone will go out the door broken.
APIs are a contract – by releasing them, you’re implicitly promising that they’ll work consistently. Too many changes on too little notice ultimately leads to too few developers.