I do not want to be tracked by 3rd parties. I do not however want to block ads either as that way, I strip my favourite publishers who are frequently not terribly rich from their income. The solution seems quite easy to me: add another state to tracking protection: "Load these resources anonymously", when Firefox would load the resource with reduced fingerprint to practical minimum (e.g. just user agent string, platform and language, fixed fonts/TZ/..., no cookies/plugins/... and limit what info can JS ask and do). A mode like this wouldn't prevent tracking completely but it would surely lessen browser profile by a great deal. Browser version: 45 ESR

(In reply to David Jaša from comment #0) > The solution seems quite easy to me: > add another state to tracking protection: "Load these resources > anonymously", when Firefox would load the resource with reduced fingerprint > to practical minimum (e.g. just user agent string, platform and language, > fixed fonts/TZ/..., no cookies/plugins/... and limit what info can JS ask > and do). Unfortunately it isn't easy. In fact, I think it likely isn't even possible. A lot of resources we block in tracking protection are basically just JS scripts that get loaded directly into the publisher's page, and there is no way to run that file, give it access to the DOM (to insert ads, tracking images or whatever), but not to give it access to the 'sensitive' parts of the DOM, because there are simply too many of them, and we can't isolate that script from the rest of the page for some bits of the DOM (and everything in it) but not others. In other words, I don't think this is fixable. François, thoughts?

(In reply to David Jaša from comment #0) > The solution seems quite easy to me: > add another state to tracking protection: "Load these resources > anonymously", when Firefox would load the resource with reduced fingerprint > to practical minimum (e.g. just user agent string, platform and language, > fixed fonts/TZ/..., no cookies/plugins/... and limit what info can JS ask > and do). This is essentially what Steve (CCed here) will be exploring during his internship. We're not sure yet about the technical details or whether or not it's going to work, but it is an idea worth looking into.

We've explored all of the ideas we had for this in bug 1298207, so unless someone finds a different workable solution, we won't be working on this.