Twitter API Did What When

On April 8th, 2009

* Changed (REST): The since parameter and If-Modified-Since header are no longer supported.

* Fixed (REST): Methods documented as requiring GET were allowing POST and not counting the rate limit correctly. These methods now require GET and return an error message if POST is used.

* Fixed (REST): The /users/show.$fmt method now thorws a 404 error if no recognized parameters are given.

* Fixed (REST): The deprecated email parameter was being silently ignored, an error is now returned.

* Fixed (OAuth): Rate limiting was incorrectly by IP only when using the Authenitcation header. This has been corrected.

* Fixed (OAuth): Error messaging for OAuth clients is now more detailed.

* Fixed (REST): Direct message objects were not returning the large user representations in json responses. They will now begin doing so.

* Fixed (REST): Calls to direct message XML methods were incorrectly displaying the nilclass root tag. This has been corrected.

* Feature (REST): Added /direct_messages/show/$id.$fmt method (where $id is the direct message id and $fmt is xml or json)

* Feature (OAuth): Added provisional support for "Sign in via Twitter" for OAuth applications. An official annoucement will follow after full support is available.
Powered by DidWhatWhen