I never got any response on this, but a small update: it's now down to about an hour for this to update correctly. Often I'll hit /users/show/<username>.json and it will return the correct value, however if I go and update the avatar a 2nd time (to the 3rd image, counting the first, original), the json file now returns the 2nd avatar (not the new, third). So the json file updates but then seems to be cached.
Is this parameter being cached in some way, or is this still a bug that's waiting to be resolved after the image-hosting move? If it's cached and it's a known time frame I can update my app accordingly, but right now I don't know that for sure. The web interface updates this parameter immediately. Any word on this? +Clint On Thu, Jun 25, 2009 at 1:46 PM, Clint Shryock <cts...@gmail.com> wrote: > I'm using the update_profile_image API call which is now working > wonderfully. The problem I'm having is the corresponding profile_image_url > attribute I'm pulling from /users/show/<username>.xml is taking hours to > update (upwards of 12 it seems). I did notice that the /<username>.xml > reflects this update immediately. > This is apparent if you're using a twitter client (say tweetie or > twitteriffic). If a user updates their profile image these apps are showing > blank/empty images because the API is still returning the old profile image > url, which no longer points to a valid file. > > I've been following and commenting on twitter issues #648, #637 and $497, > but haven't gotten feedback. Any word on what's going on here? > > +Clint >
