Speaking of static avatar URLs... how about Gravatar[1] support? [1] http://en.gravatar.com/
On Thu, May 21, 2009 at 18:14, Doug Williams <d...@twitter.com> wrote: > Thanks for your patience guys -- we realize the benefits of predictable > static URLs. It's unfortunately kind of back-burner work but we're getting > to it. As most of you can tell, the image uploading logic needs a lot of > love. > Cheers, > Doug > > -- > > Doug Williams > Twitter Platform Support > http://twitter.com/dougw > > > > > > On Thu, May 21, 2009 at 4:38 PM, Tim Haines <tmhai...@gmail.com> wrote: > >> >> Hi Clint, >> >> Thanks for that. I've added myself to the watchlist. I saw a similar >> note from 2007, so was hoping it was already done - but 'a month or >> so' sounds good to me. >> >> Tim. >> >> On May 21, 10:24 pm, Clint Shryock <cts...@gmail.com> wrote: >> > the API team is in the process of re-engineering this functionality: in >> the >> > future the current profile image will have a static URL.see: >> http://code.google.com/p/twitter-api/issues/detail?id=497#c8 >> > >> > +Clint >> > >> > On Thu, May 21, 2009 at 6:11 AM, Tim Haines <tmhai...@gmail.com> wrote: >> > >> > > Hey there, >> > >> > > I'm caching profile image urls. I'm finding quite a bit of churn, and >> > > have started wondering how I'm going to keep them up to date. >> > >> > > Is there anyway to predict or determine a profile image url from a >> > > screen name or something? The url's provided all seem to contain part >> > > of the original file name - which of course is impossible to guess. >> > >> > > If there's not a way to determine them from the screen name, is there >> > > an easy way to get a bulk update of the image urls? >> > >> > > Cheers, >> > >> > > Tim. >> > >> > >> > > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from San Francisco, California, United States
