Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can. When we get to critical mass, the advertising networks will come back with a new deal. I wonder if we can come up with a widely adopt(able|ed) fingerprint that we can mask ourselves with, do any of these identifying bits actually make the web more usable for us?
"Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can." For the fourth or fifth time this year, in response to a thread about browser privacy, I am reminded that what I really want is the ability to jail/chroot a browser. Firing up a full-blown VM for a browser ("banking profile", "twitter profile", "sketchy online store profile") is way too heavyweight and resource i…
Websites can now fingerprint a device when multiple browser instances are used
131–140 of 154 posts
Re: Websites can now fingerprint a device when multiple browser instances are used
#132Earlier quoted context omitted.
A standard UUID generated at the OS level and passed through seamlessly through a browser? Yes. Client-side control means that you can turn it off depending on TOR, private-mode, VPN, or whatever else. The technical aspects though would make the web faster and easier to deal with.
So you turn it off, and half the web stops working for you because websites don't want to serve you content unless their ad networks receive your unique hardware id from some mandatory hardware TPM? Then, since a TPM is effectively mandatory once the web can't be used without it, all media content can be DRM'd with less customer push-back. I get that the web is a mess, but is this the best idea anyone can come up wit…
Easy and seamless. Why turn it off? If you do, then the networks would just generate their own ID numbers and we're back to the same scenario as today. There's nothing technically wrong with not using it but having a stable API to program against helps a lot and is the main reason this would improve the web. Android and iOS get somewhat close to this, although both are broken and unfinished.
I'm not sure why this requires any hardware TPM or DRM though.
Re: Websites can now fingerprint a device when multiple browser instances are used
#133Earlier quoted context omitted.
"Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can." For the fourth or fifth time this year, in response to a thread about browser privacy, I am reminded that what I really want is the ability to jail/chroot a browser. Firing up a full-blown VM for a browser ("banking profile", "twitter profile", "sketchy online store profile") is way too heavyweight and resource i…
Logging in to the Guest account on OSX accomplishes what you want, no?
Re: Websites can now fingerprint a device when multiple browser instances are used
#134Earlier quoted context omitted.
I really want to just use my browser though, if it's possible to make it work without confessing all the bits that make my fingerprint.
I think those bits of information are closely tied to your browser functionalities. E.g. resolution, plugins installed. Keeping those bits for you would degrade your browsing experience. Have a look at the parameters that bring the highest amount of fingerprinting bits in your config https://panopticlick.eff.org/ then see if it possible to disable them. I think it's just plain hard.
Re: Websites can now fingerprint a device when multiple browser instances are used
#135Earlier quoted context omitted.
Cloudflare blocks access to sites behind it to users with JS enabled? Even if there's no JS on the site? 1. Is there anything the site owner can do to turn that off? 2. Is it because they inject some kind of DDoS prevention/tracking thing? This suggests crawlers load JS, which I wouldn't have necessarily assumed.
cloudflare can whitelist crawlers like google. The fact it blocks other automatic robots is more of a feature than a flaw.
Re: Websites can now fingerprint a device when multiple browser instances are used
#136Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can. When we get to critical mass, the advertising networks will come back with a new deal. I wonder if we can come up with a widely adopt(able|ed) fingerprint that we can mask ourselves with, do any of these identifying bits actually make the web more usable for us?
"Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can." For the fourth or fifth time this year, in response to a thread about browser privacy, I am reminded that what I really want is the ability to jail/chroot a browser. Firing up a full-blown VM for a browser ("banking profile", "twitter profile", "sketchy online store profile") is way too heavyweight and resource i…
Sounds a bit like local Docker for browsing?
Everyone would download the same Chrome container with the exact same clean config and software rendering so the canvas/WebGL fingerprinting yielded nothing?
Re: Websites can now fingerprint a device when multiple browser instances are used
#137I note without surprise that most of this tracking leverages JavaScript. When do we say that enough is enough? When do we finally agree that the web was better without JavaScript tracking us everywhere we go, and when do we finally admit that not all ideas (JavaScript) were good ideas? My browser works against me these days. Sad times.
The problem is not Javascript - throwing out JavaScript is like throwing out your utensils because your meal is too sweet. The problem is browsers are made by advertising entities that also leverage these same abilities.
Re: Websites can now fingerprint a device when multiple browser instances are used
#138I have been browsing the web without Javascript enabled since 2006. The worst is that once in a while you will click on a link to read some text, but arrive at a completely blank page. Many times this can be solved by disabling CSS for that page or using the Google cache, but it's still annoying. I my view requiring Javascript just to display text or pictures is completely brain-dead, web "designers" that think this…
I use ublock origin with chrome. Do I understand correctly that the simple tool to block javascript (noscript) is not available on chrome ? I'd like to disable javascript but the non-noscript recipes seem very complex ...
Re: Websites can now fingerprint a device when multiple browser instances are used
#139Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can. When we get to critical mass, the advertising networks will come back with a new deal. I wonder if we can come up with a widely adopt(able|ed) fingerprint that we can mask ourselves with, do any of these identifying bits actually make the web more usable for us?
IMO the hope lies in the fact that many vendors do not depend on privacy invasions in their main business model, e.g. Amazon or Panera will sell me roughly the same stuff regardless of which photos I was staring at yesterday. Selling my info on the side is a profitable add-on, but not strictly required for their main business. Maybe unnecessary tracking will eventually be competed away (this does require that a much…
Sure you can disable js, but for the majority the Web would be really broken without js.
As a culture, tracking is everywhere. Disabling js still logs your up, referrer and a bunch of other things.
I do like what uorigin/adblock and other extensions are doing.
Re: Websites can now fingerprint a device when multiple browser instances are used
#140Earlier quoted context omitted.
"Resist! Use adblockers, disable cookies which live over the session by default, turn off JS if you can." For the fourth or fifth time this year, in response to a thread about browser privacy, I am reminded that what I really want is the ability to jail/chroot a browser. Firing up a full-blown VM for a browser ("banking profile", "twitter profile", "sketchy online store profile") is way too heavyweight and resource i…
Logging in to the Guest account on OSX accomplishes what you want, no?
No ...
That is, unless I can easily script the destruction and recreation of the guest account, and automated install and configuration of my chrome setup ...
The idea here is that I set up chrome just how I want it and deploy and redeploy that "container" over and over - destroying it and recreating it after each use. Possibly with multiple instances running simultaneously ...