API Changes for April 1, 2009
Alex Payne
* 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
Jesse Stay
Zac Bowling
Are the direct message's recipient and sender objects updated as well?
Zac Bowling
http://twitter.com/zbowling
zbowling
they would change that since it functionally break that api.
On Apr 1, 5:54 pm, Jesse Stay <jesses...@gmail.com> wrote:
> Does this include the Social Graph API methods?
> Jesse
>
Alex Payne
Alex Payne
tomorrow, hopefully, Monday at the latest.
Damon P. Cortesi
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
Damon P. Cortesi
On Apr 1, 7:23 pm, "Damon P. Cortesi" <d.lifehac...@gmail.com> wrote:
> 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>
Damon Clinkscales
>> 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.
>
> Sorry, I meant statuses_count.
>
nor favourites_count, nor friends_count...
here's my record, in full (from /users/show/damon.xml)
$ curl http://twitter.com/users/show/damon.xml
<?xml version="1.0" encoding="UTF-8"?>
<user>
<id>756264</id>
<name>Damon Clinkscales</name>
<screen_name>damon</screen_name>
<location>Austin, TX</location>
<description>I'm a shepherd. Software engineer at VitalSource and
leader of Austin On Rails. I also build apps like
http://snaptweet.com and http://doesfollow.com. </description>
<profile_image_url>https://s3.amazonaws.com/twitter_production/profile_images/73617066/me_smile_normal.jpg</profile_image_url>
<url>http://damonc.com</url>
<protected>false</protected>
<followers_count>974</followers_count>
<status>
<created_at>Wed Apr 01 21:16:29 +0000 2009</created_at>
<id>1434142066</id>
<text>RT @ev on April Fools - There is no Twitter Pro</text>
<source><a
href="http://iconfactory.com/software/twitterrific">twitterrific</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>
April Fools?
-damon
Adrian
has about twice the amount of information as say:
http://twitter.com/users/show/WeezerOfficial.xml
Chad Etzel
>
> As of right right now: http://twitter.com/users/show/bob.xml
> has about twice the amount of information as say:
> http://twitter.com/users/show/WeezerOfficial.xml
>
FTA:
"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."
-Chad
Alex Payne
Damon P. Cortesi
http://twitter.com/users/show/ccfcrule.xml is still returning the same
data as earlier.
>
>
>
>
>
> > 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>
Damon P. Cortesi
On Apr 1, 10:15 pm, Chad Etzel <jazzyc...@gmail.com> wrote:
>
> > As of right right now:http://twitter.com/users/show/bob.xml
> > has about twice the amount of information as say:
> >http://twitter.com/users/show/WeezerOfficial.xml
>
> FTA:
> "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."
>
> -Chad
before. When this change went into effect, I started getting a lot of
users with no statuses_count showing whereas prior to the change that
was a reliable property of the user object.
Jochem Prins
returning the basic user element for some users. Weird.
Jochem
binit
show/id.xml".
Now the big problem is that in some cases following fields are
missing:
friends_count
created_at
favourites_count
utc_offset
time_zone
profile_background_image_url
statuses_count
Due to this my application buzzom.com has broken down.
Is there an alternate way of getting these fields for a particular
user?
Please suggest.
Regards,
Binit
Dossy Shiobara
> * 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.
Sweet jeebus! It's Christmas, all over again!
Thanks, Twitter gnomes.
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
Damon P. Cortesi
>
> Due to this my application buzzom.com has broken down.
> Is there an alternate way of getting these fields for a particular
> user?
> Please suggest.
>
object, /statuses/user_timeline will. I've been able to use this as a
workaround for some accounts when the fields I need don't exist, but
it doesn't work in every case.
Doug Williams
reporting.
1. http://code.google.com/p/twitter-api/issues/detail?id=409
Doug Williams
Twitter API Support
http://twitter.com/dougw
binit
It works!
You saved my day :)
Jesse Stay
Doug Williams
Jeffrey Greenberg
Grumble: just to say it, this wasn't handled well at all. The fact
that this field disappears whether due to caching or through a coding
error has the same result of completely breaking my app.
How long will it take for this issue to clear up? Days? How many
exactly? and after X days will further requests be populated
correctly?
thx,
jeffrey
http://www.tweettronics.com
Doug Williams
This is valid criticism. This bug came as a surprise to us as well. We otherwise would have given developers fair warning. Unfortunately there is no easy fix, and like a bad heart-break, time may be the only answer.
In short, the problem is with the user data cache. To get the extended information into that cache, the user object must either expire or be invalidated through some user initiated update. The expiry on the cache is rather long and you will find that inactive accounts will have abbreviated data for up to 2 weeks.
This is obviously sub-optimal, as Matt would say.
Martin Dufort
the *same* user. One result has full attributes disclosure, and the
other one has not.
I've updated Issue 409 with my results.
Martin
On Apr 2, 8:36 pm, Doug Williams <d...@twitter.com> wrote:
> Jeffery,
> This is valid criticism. This bug came as a surprise to us as well. We
> otherwise would have given developers fair warning. Unfortunately there is
> no easy fix, and like a bad heart-break, time may be the only answer.
>
> In short, the problem is with the user data cache. To get the extended
> information into that cache, the user object must either expire or be
> invalidated through some user initiated update. The expiry on the cache is
> rather long and you will find that inactive accounts will have abbreviated
> data for up to 2 weeks.
>
> This is obviously sub-optimal, as Matt would say.
>
> Doug Williams
Marco Kaiser
Obviously, all tweets returned on the /statuses/friends_timeline.xml endpoint should come from users I am following (and I manually verified that for some samples), but still some of them have <following>false</following> set. It seems to be at least consistant in a way that the same user always has the same value set for following in a result set - it just is either always wrong or always right.
Is that a known issue?
Thanks,
Marco
Marco Kaiser
Matt Sanford
Marco Kaiser
I've added the information from my mail as a comment to that issue.
Marco