They could very well have never thought of deleting a photo; it doesn't seem that there is much interest in information removal there, and I could easily see if being a very ugly manual process that no one wants to spend time doing and as such it never gets done.
Sometimes a hacker is one who is expert at programming and solving problems with a computer.
Sometimes a hacker is someone who hacks particularly, one who cuts with rough or heavy blows.
In the race to the deadline, the next release, the IPO, a lot of good engineering fails by the wayside.
Note that the delete operation merely marks the data deleted - they don't actually purge or overwrite it. Perhaps there's some kind of bug in this deleted-marking system? Kind of weird they haven't been able to fix it yet though.
Keep in mind, that when the photo features of Facebook were added, they probably didn't do it while thinking about half a billion users or whatever gazillion terabytes of photos they have to operate with. Heck, they may have even started out with simply storing photos on disk in their servers where deletion was easy as opposed to on a CDN.
Even with a small user base; if a user flags a photo for deletion -- it should get deleted. Period.
When a user presses the delete button, we...
1. Delete it from the public facing servers that we control. 2. Put a request in the queue so the backups, and thumbnails will be deleted. 3. Pray that the CDN will purge the picture eventually.
#3 is a big deal... we don't control the CDNs cache options, and can't push a 'delete' upstream so the picture might be gone 2 seconds after the deletion is completed on our end, or it might take 2 weeks.
I'd thought Facebook would have been able to engineer or negotiate better options than we do, but apparently not.
I don't really know how their photo system works - maybe it is a trivial thing to purge files from CDNs on demand - but I'm willing to give the benefit of the doubt and say never attribute to malice, what could be explained by earth-population-level scaling problems.
Also unrelated: Facebook has shown many times that they can't really be trusted on privacy issues - I never upload anything there under the illusion that I can freely delete it and it's really gone. But I don't personally believe this thing is a privacy issue they're intentionally balking on
You aren't familiar with Facebook's infrastructure and comparing working on small websites to working on something that scales to roughly 1/12 of the entire population of the planet is laughably naive.
Saying you use a "modul[ar]" approach is nothing but handwaving. You think that facebook doesn't use modules? Or doesn't have a service oriented architecture to some degree? They friggin' developed their own RPC transport!
-- Phil Karlton
This is a cache invalidation problem. Now, I don't mean to say that this is acceptable, but it is hardly simple. In the general case, it's unsolved.
Sure, deleting a file from a single datacenter is easy. Verifyably deleting it from an infrastructure the size of Facebook's is not.
Can you clarify why you think the problems are similar?
The two scenarios have entirely different constraints, this is undeniable. It's still an instance of the same basic problem: verifyably deleting the image means invalidating all caches of that image.
Don't worry a few years in Industry and you'll learn what things are really like.
i.e. There is no end of shite software that wasn't developed. Yes you can make lots of money with hodgepodge software. Welcome to Industry :)
I find it VERY hard to believe that Facebook did not plan ahead and implement an efficient method of photo deletion. If they truly did not, I seriously call upon their skills and insight in creating software for the public.
Come on Facebook ... it's deleting a damn image! This should be top priority in the modern age of personal privacy.