5 ms·
I'll look into what's happening, but in general it's expensive / complicated to delete from edge-caching CDNs. If there is a photo that gets constant traffic,
by aristus 16y ago
I'll look into what's happening, but in general it's expensive / complicated to delete from edge-caching CDNs.
If there is a photo that gets constant traffic, the edge caches will do their job of keeping it around. Poking around the Googles, it looks like this URL has been reposted a lot, which creates a self-fulfilling prophecy and will keep it around in cache.
http://www.google.com/search?q=5013_96426961157_709851157_2130600_2272342_n.jpg&hl=en&start=40&sa=N&filter=0 http://www.google.com/search?q=5013_96426961157_709851157_21...
- nfnaaron 16y agoSo you can't delete delete a picture if other people, who don't own it, like to look at it?
- waterlesscloud 16y agoNot very hard to imagine how that might be exploited in some undesirable ways.
- aristus 16y agoIt's more complicated than that and I'm talking and about edge caches in general here, not for my employer. I once saw a Flickr employee (Cal Henderson?) pluck the original Ludicorp logo out of Yahoo's edge caches. That's not to mention ISP caches and proxies, third party image search, etc, that neither you, I, Akamai, nor Facebook control. I'll look into it and see what's going on in this case.