We specify full URLs to images so that developers don't have to supply
custom code to pull in profile images and background images. It sounds
like you have a pretty unusual use case for our profile images.
For what it's worth, I think we deployed six variations of those
images, but our front end team may deploy more at any time. Similarly,
they may change up the default profile colors and such. That's out of
the control of our team.
Alex Payne - Platform Lead, Twitter, Inc.
Why use md5 on a moving target? Who knows when someone may resave an
image to compress it more.
I bet 1% compression savings translates to thousands of dollars over
Isn't the path relatively static?
Maybe you can use the file path?
Do user profile images mantain the same trailing path as the default
Maybe then a 2x daily script that uses curl with regex support to find
if any images up to a point 404. Looks like you have 5-6 known cases.
If you hit a 404 alert yourself, investigate, and make adjustments.
It sounds to me like those images are in control of designers not
developers so I would consider those images hostile at all times.
I agree, has_updated_profile_image would be good for the API. As it is
now, someone could upload a profile pic of the default, and it would
appear as not being updated, when in fact it has.
Iphone says hello.
On Sep 15, 2009, at 4:38 AM, timwhitlock