Yes, but once you have the url, why store the actual .png locally? Sure, if a user changes their profile image you may have a broken link, but you can update profile info every hour or so, thus making it a non-issue.
On Jan 5, 2009, at 12:34 PM, Peter Denton wrote: > I am storing the picture URL (ex: > http://s3.amazonaws.com/twitter_production/profile_images/40587632/blob_bigger.png) > > in a DB field on my site, then cycling through users occasionally > and updating profile content. You don't want to be hitting the api > for information like images every time a page loads. > > > On Mon, Jan 5, 2009 at 12:29 PM, tweetalkr <[email protected]> > wrote: > > Does anyone have a recomendation about whether your app should save > the twitter users pictures on site or simply access the twitter > supplied URL for a user's picture inside the app? Does this URL ever > change or does Twitter ever block access? > Patrick Minton IT Director LexBlog, Inc. +1 206 697 4548
