I can't say I was keeping any of these bugs as pets, but Matt (and all you guys) - great work. Your continuing effort is inspiring. :)
On Fri, Nov 14, 2008 at 4:15 PM, Alex Payne <[EMAIL PROTECTED]> wrote: > > I've just added the first entry to the REST API Changelog at > http://apiwiki.twitter.com/REST+API+Changelog. You'll find that we > shipped a number of fixes today: > > * Fixed: error messages returned by the API will be returned in the > format of the original request. For example, if you request > /statuses/user_timeline.json and your request incurs an error, you'll > get a response describing that error in the form of a JSON hash. > > * Security: statuses of protected users are no longer leaked by adding > them as favorites via the API. > > * Fixed: /users/show and other methods will now show you the > attributes of a protected user you are not authorized to see, but not > that user's current status. Previously, you were not allowed to see > any data about protected users with that method, but this behavior > diverged from that of the Twitter website, where a protected user's > location, description, and so forth are visible to anyone. > > * Fixed: user-defined callbacks on JSON requests will no longer be > omitted from requests that have been page-cached on Twitter's side. > If you were only seeing your callback intermittently when requesting > JSON, this should be resolved. > > * Fixed: a higher daily limit for the number of statuses you can mark > as a favorite. This should help out favorite-related bots. > > * Fixed: more informative error messages when marking a status as a > favorite via the API fails. > > Nearly all of these fixes are thanks to the inimitable Matt Sanford > (@mzsanford). If one of these was your pet bug, send him thanks. > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x > -- Geoff Barnes @texburgher
