Feature Suggestion | add privacy.trackingprotection.fingerprinting.enabled #808

Closed
opened 2019-04-01 05:55:31 +00:00 by hasux3 · 7 comments
hasux3 commented 2019-04-01 05:55:31 +00:00 (Migrated from github.com)

hello, for hardening privacy add this about:config

privacy.trackingprotection.fingerprinting.enabled ;true

hello, for hardening privacy add this about:config privacy.trackingprotection.fingerprinting.enabled ;true
Mikaela commented 2019-04-01 09:26:47 +00:00 (Migrated from github.com)

Why was this closed, Is it included to privacy.resistFingerprinting or privacy.trackingprotection.enabled, or did you confuse it as a duplicate of https://github.com/privacytoolsIO/privacytools.io/issues/809 ?

Why was this closed, Is it included to `privacy.resistFingerprinting` or `privacy.trackingprotection.enabled`, or did you confuse it as a duplicate of https://github.com/privacytoolsIO/privacytools.io/issues/809 ?
hasux3 commented 2019-04-01 11:26:00 +00:00 (Migrated from github.com)

what's your problem to close this topic?
it is new about:config rule add to version 66 to protect user against fingerprint.
privacy.trackingprotection.fingerprinting.enabled

what's your problem to close this topic? it is new about:config rule add to version 66 to protect user against fingerprint. privacy.trackingprotection.**fingerprinting**.enabled
privacytoolsIO commented 2019-04-02 03:35:28 +00:00 (Migrated from github.com)

or did you confuse it as a duplicate of #809 ?

That's exactly what happened, @Mikaela

> or did you confuse it as a duplicate of #809 ? That's exactly what happened, @Mikaela
privacytoolsIO commented 2019-04-02 03:48:59 +00:00 (Migrated from github.com)

thanks, guys.

thanks, guys.
Atavic commented 2019-04-10 19:51:33 +00:00 (Migrated from github.com)

When tracking protection is enabled, this entry adds another request to mozilla shavar servers:
"base-fingerprinting-track-digest256"

When tracking protection is enabled, this entry adds another request to mozilla shavar servers: "base-fingerprinting-track-digest256"
beerisgood commented 2019-04-11 04:30:09 +00:00 (Migrated from github.com)

@Atavic that's the reason why ghacks user.js doesn't use this and instead recommend uBlock Origin

@Atavic that's the reason why ghacks user.js doesn't use this and instead recommend uBlock Origin
Thorin-Oakenpants commented 2019-05-10 18:19:43 +00:00 (Migrated from github.com)

actually the reason the ghacks user.js doesn't use this (and in fact recently removed all Tracking Protection (TP) prefs, none of which were active, i.e they were all commented out) is

  • The same pref is used for different levels, and thus duplication of prefs to cover all options = messy
  • TP lists (and other prefs, not just list ones) are proliferating (e.g crypto, fingerprinting)
  • TP is undergoing other changes, and tie-in's to cookie settings etc: the state of which is changing on a weekly basis if you follow what's going on in studies, telemetry, nightly etc = way too much overhead to follow and keep up to date
  • TP will get turned on by default soon at appropriate levels when ready: happy to wait and just let Firefox decide when
  • Firefox has a giant UI section for TP: users can do it from the UI
  • Firefox has other places to let to control TP, e.g from the urlbar info icon, from the hamburger menu
  • Firefox is also probably going to display the number of blocked items: a counter = more visibility when it's enabled by default
  • Anyone with an inkling of privacy (e.g all the people who visit PTIO) would have an adblocker of some sort, so I don't see this as mission critical

So, excluding the overhead of trying to keep up with it, it's all just a bit pointless: All PTIO needs to do is recommend users go to the UI setting and enable x, y, z: and even then, it'll be on by default very soon

Edit: but I see they've already been added

privacy.trackingprotection.fingerprinting.enabled = true
Blocks Fingerprinting
privacy.trackingprotection.cryptomining.enabled = true
Blocks CryptoMining

actually the reason the ghacks user.js doesn't use this (and in fact recently removed all Tracking Protection (TP) prefs, none of which were active, i.e they were all commented out) is - The same pref is used for different levels, and thus duplication of prefs to cover all options = messy - TP lists (and other prefs, not just list ones) are proliferating (e.g crypto, fingerprinting) - TP is undergoing other changes, and tie-in's to cookie settings etc: the state of which is changing on a weekly basis if you follow what's going on in studies, telemetry, nightly etc = way too much overhead to follow and keep up to date - TP will get turned on by default soon at appropriate levels when ready: happy to wait and just let Firefox decide when - Firefox has a giant UI section for TP: users can do it from the UI - Firefox has other places to let to control TP, e.g from the urlbar info icon, from the hamburger menu - Firefox is also probably going to display the number of blocked items: a counter = more visibility when it's enabled by default - Anyone with an inkling of privacy (e.g all the people who visit PTIO) would have an adblocker of some sort, so I don't see this as mission critical So, excluding the overhead of trying to keep up with it, it's all just a bit pointless: All PTIO needs to do is recommend users go to the UI setting and enable x, y, z: and even then, it'll be on by default very soon Edit: but I see they've already been [added](https://www.privacytools.io/browsers/#about_config) > privacy.trackingprotection.fingerprinting.enabled = true > Blocks Fingerprinting > privacy.trackingprotection.cryptomining.enabled = true > Blocks CryptoMining
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#808
No description provided.