We should also consider the user experience. Some of my friends change their avatar daily (if not hourly). If each application caches the avatar, the user might end up with a different avatar on each application. That would especially apply to applications that do not need to update data regularly. I like the 302 redirect approach.
On Oct 9, 8:26 am, jstrellner <[EMAIL PROTECTED]> wrote: > I don't think they should do anything, but ask you guys to cache the > profile pictures yourself. By linking directly to the file, you are > increasing their Amazon costs. It doesn't take much to cache it > yourself, and then every time someone does an update, you just check > to see if the old URL that you have matches the new one, and if it > doesn't, go get another copy of it to replace your cached file. > > I am not sure if they have encouraged, or discouraged hot-linking to > their files, but it probably is the best solution to cache it, and one > that Twitturly uses. > > -Joel > > On Oct 8, 4:25 pm, Nicolas Grasset <[EMAIL PROTECTED]> wrote: > > > > > Is there a way to get a static profile picture URL when using the API, > > since picture updates will break old links? > > > My > > photo:http://s3.amazonaws.com/twitter_production/profile_images/38643882/av... > > > ... will have a different URL if I change it on Twitter, which means > > we cannot trust our local cache of events, which means we would need > > to call the APIs for all events all the time. > > > And in our case that is not really an option. > > > Thanks!!- Hide quoted text - > > - Show quoted text -
