Yesterday [Twitter announced upcoming changes to their API](https://dev.twitter.com/blog/changes-coming-to-twitter-api) and there has already been a ton of brilliant writing about the changes. For a breakdown on the changes, I recommend either [Marco Arment’s posting](http://www.marco.org/2012/08/16/twitter-api-changes) or [Dieter Bohn’s writeup on The Verge](http://www.theverge.com/2012/8/16/3248079/twitter-limits-app-developers-control). There is also commentary from [Ben Brooks](http://brooksreview.net/2012/08/twitter-bullshit/), [Matthew Panzarino](http://thenextweb.com/twitter/2012/08/17/twitter-4/), [Dan Frommer](http://www.readwriteweb.com/archives/why-twitter-just-pushed-developers-aside-to-secure-its-future.php), and [MG Siegler](http://parislemon.com/post/29582867630). Over at Daring Fireball, John Gruber has two posts, [one in response to Anil Dash](http://daringfireball.net/linked/2012/08/16/dash)[^dash] and one that summarizes his interpretation of the changes, entitled [Twitter to Client Developers: Drop Dead](http://daringfireball.net/linked/2012/08/16/twitter-drop-dead):
> So Klout, which is utter vainglorious masturbatory nonsense, that’s OK. But services like Storify and Favstar, which are actually useful and/or fun, those are no good. And don’t even get me started on Twitter turning against client apps.
The whole thing makes the development of [App.net](http://app.net) look even more important than it did just 24 hours ago.
[^dash]: [Anil Dash’s original article.](http://dashes.com/anil/2012/08/what-twitters-api-announcement-could-have-said.html)