I'm not sure if it's related to this push, but I've started to get several user objects back with no statuses_updates.
This is a somewhat blocking bug for TweetStats as I try to verify they have tweets while verifying the account. Though I can just try to enumerate through and will probably have to do an emergency update to do so. here's a sample user object I'm getting back: <?xml version="1.0" encoding="UTF-8"?> <user> <id>20176857</id> <name>Jonny Beasley</name> <screen_name>ccfcrule</screen_name> <location></location> <description></description> <profile_image_url>http://s3.amazonaws.com/twitter_production/ profile_images/78298843/Me_With_Cap_normal.jpg</profile_image_url> <url></url> <protected>false</protected> <followers_count>25</followers_count> <status> <created_at>Sat Mar 28 20:00:26 +0000 2009</created_at> <id>1408524555</id> <text>Checking out my TweetStats! http://tweetstats.com/graphs/ccfcrule</text> <source><a href="http:// tweetstats.com">TweetStats</a></source> <truncated>false</truncated> <in_reply_to_status_id></in_reply_to_status_id> <in_reply_to_user_id></in_reply_to_user_id> <favorited>false</favorited> <in_reply_to_screen_name></in_reply_to_screen_name> </status> </user> dpc On Apr 1, 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 athttp://bit.ly/api_changelog. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
