I agree that having gravatar-style service for twitter avatars will be tremendously useful!
Even better, if avatars are stored in .png ONLY, in which case you can just use the url without even checking with gravatar-like service. For example just put avatar.twitter.com/23423423423423.png (by twitter id) or maybe even by username.png Done! The http configuration will then have a custom directive to return a default avatar if user-specific one does not exist The png is good choice because it can be animated and support transparency. Just convert uploaded jpg or gif images to .png and they good to go. Then, a web based app can just generate a path to avatar based on username or userid and at least the default avatar will be shown. If user updates the avatar, then the current one will be shown, eliminating the need to check with API. Developers can add ?timestamp to image to disable browser caching if they want to. On Feb 17, 5:38 pm, Abraham Williams <4bra...@gmail.com> wrote: > I would image that implementing S3 versioning would be pretty easy and would > rid your systems of a whole bunch of complexity. > > http://groups.google.com/group/twitter-development-talk/browse_thread... > > Abraham > > > > On Tue, Feb 16, 2010 at 12:51, Raffi Krikorian <ra...@twitter.com> wrote: > > probably more than a single day :P > > > yes - we have thought about it... its low on our priority list right now, > > however. > > > On Tue, Feb 16, 2010 at 12:17 PM, Peter Kieltyka <peter.kielt...@gmail.com > > > wrote: > > >> Hey guys, > > >> I was wondering if twitter has any plans to offer a global URL to each > >> user's profile pic? This would be very handy for third party apps > >> built on top of Twitter. Grabbing the profile_image_url which links > >> directly to the S3 URL, is susceptible to change and requires a lot of > >> effort on the dev's part to make sure its always up to date and > >> working. > > >> Consider something like gravatar.com, but for twitter users. There is > >> the thehttp://tweetimag.esservice, which works great, but for > >> something so close to the infrastructure I feel this type of service > >> should be built and supported by twitter itself. > > >> I think tweetimag.es has nailed the API as in: > > >> ie. Hopefully something like: > > >>http://twimg.com/pkieltyka_m > >>http://twimg.com/pkieltyka_n > >>http://twimg.com/pkieltyka_b > >>http://twimg.com/pkieltyka_o > > >> if twitter continue's to use S3, it would be very simple to setup a > >> CNAME for twimg.com that points to an S3 bucket and each reference to > >> a username's profile can be down-cased and append the _SIZE. Simple. > > >> Should take about a single day to implement this :) > > >> Cheers. > > >> Peter > > > -- > > Raffi Krikorian > > Twitter Platform Team > >http://twitter.com/raffi > > -- > Abraham Williams | Community Advocate |http://abrah.am > Project | Out Loud |http://outloud.labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private. > Sent from Seattle, WA, United States