Last time I discussed it was here:
The issue with lookaside URLs resolving to 404 error I mention was fixed (by FB) quite a while ago, but there’s definitely a history of flakiness here with FB profile photos.
As far as why folks don’t notice this, it’s hard to say. However, the reason I do is that I’ve got a debug type header on all pages of my app which has some user info in it, including profile image. (So I quite regularly see my own profile image come and go…)
#shrug
A for sure “fix” is to abandon the idea of dynamic profile photos and just force the profile photo “:saved to s3” at some point.
It occurs to me that one could also add a make changes to current user in one’s LOGIN workflow and force profile image = fb profile photo. (Which seems very ham handed, but whaddyagonnado?)