Uploading the same file to Twitter twice in a row results in 2 unique URLs. For example:
http://a3.twimg.com/profile_background_images/63273103/avatar-200.png http://a3.twimg.com/profile_background_images/63273237/avatar-200.png So after you upload the background image save the URL and either do HEAD request to see if it is still active or compare it to the URL in users/show. Abraham On 2009-12-31, Kyle Mulka <repalvigla...@yahoo.com> wrote: > I've noticed that you keep the filename. That was kind of annoying for > other reasons: > > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1f63694495c02ff/a713748c19c35895 > > If I just check the filename, I can't be sure that the file wasn't > changed by the user. It would be nice if the account/ > update_profile_background_image function could guarantee that the > image URL returned was the actual image I uploaded. (with whatever > filtering you want to apply) > > > -- > Kyle Mulka > Founder, Congo Labs > http://twilk.com > > > On Dec 30, 8:03 pm, John Adams <j...@twitter.com> wrote: > > On Dec 30, 2009, at 4:21 PM, Kyle Mulka wrote: > > > > > My application uploads a background image on a user's behalf. I want > > > to be able to figure out if they are still using the background image > > > at some future point in time. > > > > The filename might work as a test for this, instead of the > > computationally expensive MD5 on an image hack. > > > > We still retain the original file (basename) on images. > > > > -j > > > > --- > > John Adams (@netik) > > Twitter Operations > > > j...@twitter.comhttp://twitter.com/netik > -- Abraham Williams | #doit | http://hashtagdoit.com Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private.