Fantastic news. Are the direct message's recipient and sender objects updated as well?
Zac Bowling http://twitter.com/zbowling On Wed, Apr 1, 2009 at 5:34 PM, Alex Payne <a...@twitter.com> wrote: > > (Not an April Fool, we promise. We don't enjoy "humor".) > > * Feature (REST API): We now return the same representation of User > objects throughout the API. This representation contains all of the > attributes we make available via the API. > > A bit more about this change: > > Previously, these "full" User objects were only available via the > /users/show and /account/verify_credentials methods. If your > application has been making requests to these methods just to get > extra User attributes, you no longer need to do so. We've had many, > many requests for these extra attributes to be available everywhere, > so we hope to see you all making use of them! > > Please note that this new extended view of User objects may not appear > for all users immediately. As cache expiry occurs for users in our > system, the extra attributes will show up. Don't be surprised if this > takes multiple days for inactive users. > > Please also note that if your application is operating in a highly > bandwidth-constrained environment, you may want to proxy requests to > strip out attributes that aren't relevant to your client. The > additional bytes over the wire should not impact the vast majority of > platforms, in our estimates. > > As always, you can keep up with these changes at http://bit.ly/api_changelog. > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x >
