user.js: [user.js suggestion] Do Not Track and Global Privacy Control signals [redundant with dFPI]
Wouldn’t it be good to enable them by default, or aren’t they enabled because of fingerprinting?
<spoiler>
privacy.globalprivacycontrol.enabled
privacy.globalprivacycontrol.functionality.enabled
privacy.globalprivacycontrol.was_ever_enabled
privacy.donottrackheader.enabled
</spoiler>
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (9 by maintainers)
I am hoping to convince you to reopen Issue #1542. The GPC concept has made a lot of progress and it I think it is worth re-evaluating. Consider the following:
And some counter examples to @Thorin-Oakenpants earlier points from this comment,
The California DOJ cares and the GPC header under the CCPA is being enforced. From the August 24, 2022 CA AG’s Press Release:
I don’t know off-hand if there are any GDPR enforcement actions, but I am sure the EU wouldn’t hesitate to enforce if they felt it was appropriate.
Currently, GPC isn’t included in your
user.jsI believe it would require the addition of two additional prefs:But you would know about this bit better than than I.
Anyway, I’ll get off my soapbox. Here’s hoping you reconsider!
I didn’t mean that literally no one cares. Obviously some do re enforcement and usage. But in terms of effectiveness it is statistically moot, and it is practically obsolete with dFPI + sanitizing - hence NO ONE CARES.
It will change when Mozilla changes it. Go ask them to do it, it’s all set up.
@Thorin-Oakenpants It has been a couple years since this was last discussed, I’m here to pester you about this once more. (sorry…)
More US states have enacted privacy laws mandating the GPC signal be respected, and setting up a framework for penalties or lawsuits if it is not respected.
Additionally Firefox has now enabled by default in Private Browsing mode (as of version 120) and Brave has enabled it by default for all users.
In my eyes, there is no cost to enabling this by default
But my strongest argument is simply why not? If the only argument against it is “nobody cares” and it becomes clear that many people do actually care, and enabling it wouldn’t harm anything, then why not enable it, if it improves things for ~50 million potential users, and doesn’t negatively impact the rest?
It’s okay. I’ll just add it to my
user-overrides.jsand call it a day. Thanks for your time.FYI: unlike DNT, the Global Privacy Control is legally binding, but from my understanding that applies exclusively to California and Colorado. GPC wouldn’t mean anything for the rest of the world, at least not now. also see -> https://bugzilla.mozilla.org/show_bug.cgi?id=1670058#c1
I still feel like you may not be appreciating the different focuses of dFPI and GPC, as I understand it dFPI does one thing, GPC another.
(edit: to be more explicit, dFPI seems only useful in the context of preventing tracking specifically cross site tracking. Whereas GPC, is a signal not to share or sell personal data, and applies not just to cross site/3rd party trackers, but first parties as well, this is something dFPI cannot address, so no, I do not agree that GPC and dFPI are redundant, I see them as complementary layers with some overlap but considerable differences).
My understanding is dFPI is an effective tool at preventing cross site tracking, through state partitioning (correct?). I accept that that is a better solution for 3rd party trackers and tracking cookies and the like. But I don’t believe dFPI has any impact on first party abuse of your personal information.
If you live in the EU, you enjoy stronger privacy rights than most. I believe GDPR mandates no business can sell or share your personal info without your consent. Most of the rest of the world does not have that right. In the states, we must manually opt-out, and even then, that opt-out is only legally required in a number of states. GPC is the most efficient method to perform that opt-out From 1st parties (as well as 3rd parties) selling or sharing your personal information please correct me if I am wrong and dFPI can do something in that context?
once again
even if statistically it went up, it doesn’t really DO anything for us because dFPI. Tor Browser doesn’t care and neither should we. Tor Browser doesn’t even care about blocking trackers, because FPI. Capsice?
changing it is just another pref to add, another thing to read in the user.js, another thing to be asked about … the answer is no - AND it will be an outlier in fingerprints INCLUDING headers (passive fingerprinting … so no, just … NO
How is it send if they are blocked. 🤔