WordPress.com Implements the Twitter API 39
This morning Matt Mullenweg announced on his blog that WordPress.com has enabled posting and reading blogs via the Twitter API. Now any Twitter app that supports a custom API URL (Tweetie is one such) can be used to either post updates to a WordPress.com blog, or to read updates from blogs to which one has subscribed. Dave Winer calls the move by Automattic, WordPress.com's parent company, "deeply insidious," and notes that 10 years ago he did a similar thing in his Manila blogging platform when the Blogger API came out. Winer opines that Automattic's move has made the Twitter API into an open standard, due to WordPress.com's large base. Winer notes (in a comment on the above-linked post), "The fun starts if they [WordPress] relax some of the limits of the Twitter API and fix some of the glaring problems."
Just another API (Score:3, Informative)
They're just adding a feature for who use Twitter apps. It's not like this will become the only supported way to post or read blog replies, so what does it matter? They do support other blog posting API's too.
Heh. (Score:0, Informative)
Drupal has had a Twitter addon for ages now.
Misleading summary... (Score:5, Informative)
I thought it strange that this move would be called "deeply insidious". Here's the context in Dave Winer's blog post:
Since there is effectively now dozens of twitter clients capable of connecting to wordpress via this api, the api becomes a de-facto standard for accessing blogs.