we have a caching issue regarding embedded <user> objects in <status>
objects. its something that is on our minds to get repaired and rectified.
so, yes, this is a known issue.
our current suggestion, and i apologise for the pain, is to call users/show
on the user to make sure that you have the most recent user information of
the user you are looking at. alternatively, their latest tweet -probably-
has the most recent data.
On Thu, Mar 25, 2010 at 1:45 PM, vsr <rockrai...@gmail.com> wrote:
> Have a look at profile_image_url in API response for @jack's first
> tweet at http://api.twitter.com/1/statuses/show/20.xml
> and any other recent tweet (
> The profile image url is different in these two tweets though they are
> for the same person, @jack.
> Does this mean that the profile_image_url is(was?) linked to a tweet
> (and not to user) ? Is this a known issue?
> I don't have any problem with tweets giving me old profile image url
> as long as they are valid and working. The profile image returned by
> tweet id 20 gives a 403 most of the time.
> To unsubscribe from this group, send email to twitter-development-talk+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
Twitter Platform Team
To unsubscribe from this group, send email to
twitter-development-talk+unsubscribegooglegroups.com or reply to this email
with the words "REMOVE ME" as the subject.