The problem: 1. The developer changes the icon of an extension on AMO 2. The icon is updated on AMO and in Facebook app 3. The icon of this add-on isn't updated when displayed in users profile as a 'favorite' (*) even when the profile is updated with a fresh setFBML (!) Looks like this might be due to Facebook's aggressive caching of images in the profile. Suggestion: when adding FBML to user's facebook profile, add '?RANDOM_NUMBER' to every add-on icon's URL so facebook re-fetches the most up-to-date icon.
Adding a random number would also destroy our netscaler caching on this end. I'll come up with something from the last modified date.
(In reply to comment #1) > Adding a random number would also destroy our netscaler caching on this end. I'm not sure destroying the cache on your end is a problem specifically in this case, as facebook is very aggressive with caching the images on their end. This means that the Mozilla servers are hit only once - when the user updates the profile. I think a simple solution can be used, and once this becomes critical (millions of users constantly updating their profiles) - a new, more elaborate one can be deployed...
Fixed on trunk/staging. The strtotime() value of the last modified date is appended to icon urls now to make sure Facebook's cache is updated when appropriate.