This is related to the caching changes that came as a result of
yesterday's push [1]. It shouldn't be a problem for active users, and
will be fully fixed after less active users expire from the cache.

1. 
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f79c44d905a3e83d#

Doug Williams
Twitter API Support

On Apr 2, 5:07 pm, "dean.j.robinson" <dean.j.robin...@gmail.com>
wrote:
> I noticed this because I've got some code that checks the utc_offset
> and noticed that it was missing.
>
> For my hahlo account verify_credentials is returning this (appears to
> be missing colours, utc_offset, fav counts etc etc):
>
> <?xml version="1.0" encoding="UTF-8"?>
> <user>
>   <id>7097682</id>
>   <name>Hahlo.com</name>
>   <screen_name>hahlo</screen_name>
>   <location>Newcastle, Australia</location>
>   <description>The best iPhone/touch style Twitter app. Hahlo 4 will
> be oAuth-tastic.</description>
>   <profile_image_url>http://s3.amazonaws.com/twitter_production/
> profile_images/53694164/favicon_normal.png</profile_image_url>
>   <url>http://hahlo.com</url>
>   <protected>false</protected>
>   <followers_count>1097</followers_count>
>   <status>
>     <created_at>Tue Mar 31 00:52:42 +0000 2009</created_at>
>     <id>1421396597</id>
>     <text>great news from twitter, all @replies are now part of the
> replies timeline, effective immediately, you don't need to change a
> single thing</text>
>     <source>&lt;a href=&quot;http://dev.hahlo.com/
> &quot;&gt;&#948;.hahlo&lt;/a&gt;</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>
>
> for my deanjrobinson account it returns this:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <user>
>   <id>782566</id>
>   <name>Dean Robinson</name>
>   <screen_name>deanjrobinson</screen_name>
>   <location>Newcastle, Australia</location>
>   <description></description>
>   <profile_image_url>http://s3.amazonaws.com/twitter_production/
> profile_images/54336181/fie-12_normal.png</profile_image_url>
>   <url>http://www.deanjrobinson.com</url>
>   <protected>false</protected>
>   <followers_count>375</followers_count>
>   <profile_background_color>FFFFFF</profile_background_color>
>   <profile_text_color>323232</profile_text_color>
>   <profile_link_color>676767</profile_link_color>
>   <profile_sidebar_fill_color>F5F5F5</profile_sidebar_fill_color>
>   <profile_sidebar_border_color>EEEEEE</profile_sidebar_border_color>
>   <friends_count>97</friends_count>
>   <created_at>Tue Feb 20 08:02:11 +0000 2007</created_at>
>   <favourites_count>65</favourites_count>
>   <utc_offset>36000</utc_offset>
>   <time_zone>Sydney</time_zone>
>   <profile_background_image_url>http://s3.amazonaws.com/
> twitter_production/profile_background_images/1486932/twitterbg.jpg</
> profile_background_image_url>
>   <profile_background_tile>false</profile_background_tile>
>   <statuses_count>2157</statuses_count>
>   <notifications></notifications>
>   <following></following>
>   <status>
>     <created_at>Thu Apr 02 22:55:57 +0000 2009</created_at>
>     <id>1441582913</id>
>     <text>hmmm, installed littlesnapper update, and now I've got four
> copies of every screenshot... I think thats a bug.</text>
>     <source>&lt;a href="http://www.hahlo.com/"&gt;Hahlo&lt;/a&gt;</
> 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>
>
> Is this connected to the recent change that adds the full user object
> to all api calls?

Reply via email to