Twitter API Did What When

In March 2009

* Fixed: New accounts would silently allow over sized values in some profile fields and the bad data would later be truncated. The system now correctly reports an error.
* Fixed: The /friends/ids and /followers/ids no longer require authentication for protected users.

* Fixed: The /friends/ids and /followers/ids now support the callback parameter for JSON.

* Fixed: Statuses ending in "..." are no longer incorrectly trimmed when displayed on twitter.com.
* Feature (Search): You can now search for ticker symbols like $DIA.

* Feature (OAuth): Added an oauth_access_type parameter to the authorize URL so applications can specify read/read write per user.

* Fixed (OAuth): There was a delay after an application was approved where requests would not work. This has been corrected.
* Feature (OAuth): The OAuth closed beta has ended and OAuth is now open to all for a more extensive beta.
* Feature (Search): Trend reports are now available for current, daily, and weekly timeframes.

* Feature (REST): Timeline methods now support a max_id parameter. (Issue #152)

* Fixed (REST): Methods with id parameters now accept user_id and screen_name parameters for disambiguation. (Issue #354)
* Feature (REST): Added rate limit status to HTTP response headers as X-RateLimit-Limit and X-RateLimit-Remaining

* Fixed (OAuth): Fixed an issue where application icons were not being saved. Icons missed will show up eventually but developers can re-upload to fix the issue.

* Feature: Added a /friendships/add/[screen_name]page for 3rd party sites to refer web users to for following new people.
* Feature (REST): statuses/replies now includes mentions. Announcement Thread.

* Feature (REST): Added rate limit HTTP response header X-RateLimit-Reset.

* Fixed (REST): The since_id parameter on direct messages had recently stopped working and was repaired.
Powered by DidWhatWhen