3 ms·

Like not implementing cookies, LocalStorage, screen resolution info, font enumeration, canvas, WebGL, WebRTC, etc etc? It's probably realistically possible to

Like not implementing cookies, LocalStorage, screen resolution info, font enumeration, canvas, WebGL, WebRTC, etc etc? It's probably realistically possible to disable those with the existing browsers. Problem is, that will also break sites that expect you to have all those available. And it's said that there are too many of those (I never saw a proper analysis, though) Just consider: there are sites (one of my favorite pizza delivery sites does that) that break if you just block Google Analytics ga.js (or their newer versions, whatever they're called) scripts. Just because they have stuff like `_gaq.push` hardcoded into click handlers and if those raise exceptions, they fail.

snakeanus 9y ago
Cookies are still needed for site logins so it would be quite difficult to get rid of them, it would be possible however to enable them only for the sites that you are planing to log into. As for local storage, I only needed it for some greasemonkey extensions. Do legit sites actually use it? > font enumeration, canvas, WebGL, WebRTC I have all of these disabled for the last 2 years or so actually and I don't feel like I miss anything. Only a few non-important sites need these. > Just consider: there are sites (one of my favorite pizza delivery sites does that) that break if you just block Google Analytics ga.js (or their newer versions, whatever they're called) scripts. Just because they have stuff like `_gaq.push` hardcoded into click handlers and if those raise exceptions, they fail. I think that uBlock Origin avoids that if you have the experimental filter enabled.
- mutant77 9y ago
  You need localStorage to login in your mozilla account - I block it and lost access to my account.
marcosdumay 9y ago
Firefox has an extension called "self destructing cookies" that implements those the way they should be done everywhere. There is absolutely no need for font enumeration. A browser can decide do download fonts it does not have from the site (what will indeed open it to some tracking), or use another cache (with other, different tracking possibilities). But any way it chooses, it just needs to cache the fonts locally to avoid most of the tracking. There's no reason for local storage to permit 3rd party tracking. WebRTC was a mistake, and WebGL although well meant is so complex that will never work well. A lot of out javascript signature could be simply removed without any ill effects.
- icebraining 9y ago
  it just needs to cache the fonts locally to avoid most of the tracking. Caching is one of the ways of tracking you. If site A says it needs some custom font, the browser will have to download it. If then site B (affiliated with A) asks for the same font, and the browser loads it from cache instead of asking site B, then it knows that you've been to site A.

snakeanus 9y ago

Cookies are still needed for site logins so it would be quite difficult to get rid of them, it would be possible however to enable them only for the sites that you are planing to log into. As for local storage, I only needed it for some greasemonkey extensions. Do legit sites actually use it? > font enumeration, canvas, WebGL, WebRTC I have all of these disabled for the last 2 years or so actually and I don't feel like I miss anything. Only a few non-important sites need these. > Just consider: there are sites (one of my favorite pizza delivery sites does that) that break if you just block Google Analytics ga.js (or their newer versions, whatever they're called) scripts. Just because they have stuff like `_gaq.push` hardcoded into click handlers and if those raise exceptions, they fail. I think that uBlock Origin avoids that if you have the experimental filter enabled.

mutant77 9y ago
You need localStorage to login in your mozilla account - I block it and lost access to my account.

marcosdumay 9y ago

Firefox has an extension called "self destructing cookies" that implements those the way they should be done everywhere. There is absolutely no need for font enumeration. A browser can decide do download fonts it does not have from the site (what will indeed open it to some tracking), or use another cache (with other, different tracking possibilities). But any way it chooses, it just needs to cache the fonts locally to avoid most of the tracking. There's no reason for local storage to permit 3rd party tracking. WebRTC was a mistake, and WebGL although well meant is so complex that will never work well. A lot of out javascript signature could be simply removed without any ill effects.

icebraining 9y ago
it just needs to cache the fonts locally to avoid most of the tracking. Caching is one of the ways of tracking you. If site A says it needs some custom font, the browser will have to download it. If then site B (affiliated with A) asks for the same font, and the browser loads it from cache instead of asking site B, then it knows that you've been to site A.