@Carlos: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/85c582baac05694b/f20b1b4f6b42207c?#f20b1b4f6b42207c
On Thu, Apr 9, 2009 at 11:14, Carlos Crosetti <carlos.crose...@gmail.com>wrote: > I got mu friends timelines btoken today because you changed from POST to > get, now I aligned properly. > > Would be nice from you tellling this changes in advance. Areyou doing > release management? > > Best regards,, Carlos > > On Thu, Apr 9, 2009 at 12:20 PM, Matt Sanford <m...@twitter.com> wrote: > >> >> Hi all, >> >> Sorry for the late email but the deploys yesterday ran late and we >> didn't get a chance to compile the change log. And a doozy of a change log >> it is with 10 entries. Other things were deployed as well but here are the >> 10 API-facing changes: >> >> * Changed (REST): The since parameter and If-Modified-Since header are >> no longer supported. >> » Discussed at http://bit.ly/19JZme >> >> * 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. >> » Discussed at http://bit.ly/o38Dl >> >> * Fixed (REST): The deprecated email parameter was being silently >> ignored, an error is now returned. >> » Discussed at http://bit.ly/4APnTx >> » See: http://code.google.com/p/twitter-api/issues/detail?id=353 >> >> * Fixed (REST): The /users/show.$fmt method now thorws a 404 error if >> no recognized parameters are given. >> » This is a part of the previous issue and many complaints about the >> user @show being returned as a default >> >> * Fixed (OAuth): Rate limiting was incorrectly by IP only when using >> the Authenitcation header. This has been corrected. >> » See: http://code.google.com/p/twitter-api/issues/detail?id=376 >> >> * Fixed (OAuth): Error messaging for OAuth clients is now more >> detailed. >> » See: http://code.google.com/p/twitter-api/issues/detail?id=403 >> >> * 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. >> » See: http://code.google.com/p/twitter-api/issues/detail?id=406 >> >> * Feature (REST): Added /direct_messages/show/$id.$fmt method (where >> $id is the direct message id and $fmt is xml or json) >> » See: http://code.google.com/p/twitter-api/issues/detail?id=369 >> » Note: Still needs to be added to the documentation >> >> * Feature (OAuth): Added provisional support for "Sign in via Twitter" >> for OAuth applications. An official annoucement will follow after full >> support is available. >> » More on this to come in subsequent mails. I need to get another >> piece in place first. >> >> There were also a collection of other fixes which included fixing the >> "Sign out" link on the OAuth authorization page. >> >> Thanks; >> — Matt Sanford / @mzsanford >> >> > > > -- > Carlos Crosetti > -- Abraham Williams | Hacker | http://abrah.am @poseurtech | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private.
