5 ms·
Cloudflare f*cked up big time. It's not the responsible for other third parties to clean up the mess. Especially it won't happen 100% world wide anyway, there a
by frik 10y ago
Cloudflare f*cked up big time. It's not the responsible for other third parties to clean up the mess. Especially it won't happen 100% world wide anyway, there are too many parties who have indexes (public or private).
In the end Cloudflare should be held responsible. It also puts the whole CDN service business in a bad light.
- jacquesm 10y agoI never liked CDN's because I don't like monocultures and the whole 'we decrypt your traffic but we can be trusted' bit defeated the purpose of HTTPS to begin with.
- LoSboccacc 10y agoIt's convenient for content publisher and reduce infrastructure costs a lot. Just have the authenticated/editing part served directly and the published content trough cdn.
- jacquesm 10y agoSo, retrospectively speaking: Was it worth it?
- LoSboccacc 10y agoto us, yes. a large customer signed up and we had a 300x traffic spike overnight, all eaten up by cdn. the first impression for a startup matters and them testing the service unannounced could have gone wrong in so much many ways.. cloudflare literally saved the day. the publishing part needs to be designed to leverage caching properly tho. however it's much easier to setup cloudflare+custom rules than a cdn push-on-change service
- deanclatworthy 10y agoExcept it is the responsibility of the third parties to clean up the mess. Cloudflare has no control over their infrastructure. Forget the blame game for a minute: there is personally identifiable information of the search engines users sprayed all over their cache. At this point it doesn't matter who put it there, there's a moral responsibility to clean this up, for the greater good.
- claudius 10y agoYes. And once it is cleaned up, send Cloudflare the bill. And once they go bankrupt, send the executive officers and the shareholders the bill. And once they go bankrupt, make sure they are still held responsible for the damage inflicted and that nobody that incompetent tries to run a major business damaging millions of people’s lives ever again.
- deanclatworthy 10y agoI guess we will have to agree to disagree on this one. If nginx does the same, or apache would you send them a bill also? This is a really really shitty mistake. CF hasn't handled it well. But it could have happened to anyone.
- claudius 10y agoYou are of course responsible for the tools you use, so if I use nginx and it has a bug, I won’t send them the bill. A better analogy would be to crash your client’s car into the building of a competitor and then complain if the competitor doesn’t repair that car immediately because it makes you look bad and it is for the greater good for your client to have a working car. This is what happened! Cloudflare took their clients’ cars (their data), crashed them into random buildings all over town (Google, Bing etc.) and now complains that Google and Bing don’t get their act together to repair those cars (remove the private data from the public internet). If Amazon Prime took your car to do your grocery shopping and then crashed it into Walmart, would you really complain that Walmart can’t send the bill to Amazon Prime for the clean-up?
- fauigerzigerk 10y agoAnd once you have done all of that you will have to nationalize all but the smallest businesses because no one in their right mind will invest in anything any more. As a result, tax payers will have to foot the bill for all further mistakes.
- anonymfus 10y ago>Cloudflare has no control over their infrastructure. It has via robots.txt.
- Esau 10y agoI agree. Also, I have to admit to liking this because of the way Cloudflare has treated Tor users. Feels like karma.