5 ms·
How about not leaking to third-parties? I value my privacy and I wish Mozilla would too.
by aw3c2 13y ago
How about not leaking to third-parties? I value my privacy and I wish Mozilla would too.
- rnyman 13y agoRobert here, Editor of Mozilla Hacks. We cover all kinds of resources for developers, especially with a strong focus on open source and technologies. If you are interested in knowing more about privacy, please get in touch with the people behind jsDelivr, write a comment to the blog post or similar. Thanks.
- aw3c2 13y agoHi Robert, sorry I did not realise that this was not a Mozilla project. The post sounds like it is and the site suggests it is a "hack" by Mozilla.
- rnyman 13y agoNo worries. The name of the web site is Mozilla Hacks, and we talk about everything open source/Open Web. I've added a note at the beginning of the post to be more clear.
- _puk 13y agoSorry, I don't get the comment. Leaking what? Your publicly available JS libraries? or is this a more general Mozilla bashing comment? The service itself looks great, and the versioning is exactly what I'm after.
- pgeorgi 13y agoUsers requesting files from CDN leak metadata. I guess, browsers could provide a separate cache for CDN domains that's _really_ long lived (there's a certain guarantee that files won't change there) and also send requests there with no referer at all times.
- aw3c2 13y agoSorry, I thought it was obvious. Requesting assets from third-party websites leaks that I have been visiting your site to the third-party. Now imagine having a big CDN that many websites use and you can spy on a lot of unsuspecting users.
- SEMW 13y agoSurely the correct solution to that is to control the information your browser will send to the CDN, not to try and stop web designers from using CDNs for everyone. The way requesting assets leaks the page you're visiting is through the referer header, so if you want to prevent that, use an add-on that lets you control that header, like https://addons.mozilla.org/en-US/firefox/addon/referrer-control/ https://addons.mozilla.org/en-US/firefox/addon/referrer-cont... .
- AdrianRossouw 13y agoI don't think making the entire toolchain more complex with extra edge cases that would need some kind of centrally managed white list, is more correct than 'just dont do that'.
- chc 13y agoJust don't do what? Receive the information you are sending them? If you don't want someone to have this information, the sensible thing is not to offer it. I cannot conceive of any way in which sending the information and then yelling at the recipient for receiving it is "more correct" than just not telling people things you don't want them to know.
- hackinthebochs 13y agoWhy don't site operators take responsibility for themselves to not leak their users information unnecessarily? We've taken it upon ourselves to chastise any web property that doesn't properly hash their passwords--we could just have easily say "if you don't want your password to other sites leaked, use different passwords". But we recognize the unfair burden we are placing on end users in that case. The case with CDNs and information leak is similar.