Facebook may have set near-infinite Expires/Cache-control headers on their static content, since it never gets overwritten. In that case, the CDN never goes back to the origin to check if the file is still there. The CDN they are using probably does have the ability to explicitly remove files (e.g., to respond to DMCA take-down notices), but probably doesn't have the ability to do this at Facebook picture deletion scale.
In other words, Facebook probably can't do much about it unless they get the CDN provider to make a big investment, build their own CDN, or switch to another provider that does support it (usually a costly decision).
So while things have been bad in the past--they're getting better. Having everyone try to use s3 as a CDN has really forced the industry to evolve.
And in the case of major CDN providers like Level 3, removing assets is dead simple. They provide an API for you to pass assets to expire immediately. Or barring that, having a person spend 5 seconds on the keyboard to log into the control panel and paste in the URL to kill.
It is possible - the author of the Ars article had his pictures erased after writing the article.
Few people, even technologists, can grasp what it means to have 800 million users. Anything involving individuals just logging in is a non-starter.
Even Google can provide that level of support.
They had $4 billion in cash before the IPO. They'll have $9 billion after it.
Its simple. Minority concerns like this don't upset enough of their users to impact their bottom line in any meaningful way so they don't do anything about it.
The more this becomes public the more likely it is that stories will surface about how "my life was destroyed because FB didn't actually delete the photo and now I need to be compensated" and there will be a whole bunch of lawyers waiting in the wings to take up their case. They may wait until the IPO has been completed...!
#2) Anyone with access to the link to the CDN had access to the original photo. So this really doesn't protect someone from viewing your photos you wanted to delete - since if they wanted it before they could have had it.
So ultimately this should not bug you the greatest of all the bad things they have done. The ultimate blame belongs to the person who uploaded the photo to Facebook and then later wanted it deleted.
How this was not made a priority zero, drop-everything-and-fix-this-crap-yesterday internally is beyond my comprehension. I hate to think of the condition of their internal systems if they can't even get files deleted from their CDN in a timely manner.
3 years is not a timely manner. A month and a half (their target, FTA) is not a timely manner.
A few seconds to a minute would be great, thanks.