I have not looked at this so this is mostly curiosity.
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
short time.
Isn't the path relatively static?
/images/default...
Maybe you can use the file path?
Do user profile images mantain the same trailing path as the default
image?
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.
--
Scott
Iphone says hello.
On Sep 15, 2009, at 4:38 AM, timwhitlock
<[email protected]> wrote:
I notice today that Twitter has created a new default profile pic;
e.g:
http://s.twimg.com/a/1252980779/images/default_profile_1_normal.png
Great. That's broken some of my algorithms on Twitblock.org.
(identifying re-used images)
I can fix that. I'll just add the new MD5 to my app config.
But, wait. Did I spot some different colours?
Yes, that example is only one; e.g.2:
http://s.twimg.com/a/1252980779/images/default_profile_2_normal.png
a. Can Twitter tell use how many there are of these?
b. How about a user object property "profile_image_default" (true|
false) ?
c. How about Twitter start notifying the developer community of
changes?
