> Since the competition winners were announced, the API's not even been mentioned on the blog

There is an entire site dedicated to applications on our API -- and you are on it! I refer people here all the time when they are looking for functionality we don't offer.

> Apps and wrappers have had no publicity or support from the SE team

See above.

- http://meta.stackoverflow.com/search?q=user:1+stackapps
- http://twitter.com/#!/codinghorror/status/23849465316118529

(and that doesn't even cover the times I've mentioned it on other child meta sites)

Of course this site is also linked as "api/apps" from the footer of *every site we operate* and prominently on the blog.

> So how about an update with some read only additions leading to eventually a writeable API.

The API will absolutely be revised this year. The trick is that we're still changing a lot of things about the core engine, so it's better to wait until things stabilize and roll out a stable API after we've worked out all the kinks.

The emphasis on **any public API** is not *speed of revision* but *stability*. Anything else, but I'm sorry, that's not the way I'm comfortable running this company.