📝 Correction | about:config section *desperately* needs warnings. Especially on resistFingerprinting. #2298
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#2298
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
The
about:config
section has practically no warnings on reduced Firefox functionality. This is huge as many people rely on PTIO, and don't actually know the effects of what they're modifying in about:config when they scroll down and follow the instructions. This could potentially be both harmful to Firefox and to the overall privacy community. I would not be surprised if many went "ugh, my websites aren't working, guess I'll just go back to Chrome and give up" after following the instructions on PTIO with no warnings.Why I am making the suggestion
I regularly browse r/Firefox and I have for months. Support for Firefox is available from the community there, and there are common posts about certain websites not working/laggy performance/etc. A lot of the time these issues are due to
privacy.resistFingerprinting.
Again, this is a very common issue for people, so here are just a few examples with just
privacy.resistFingerprinting
.Example 1
Example 2
Example 3
Example 4
Example 5
Example 6
Example 7
Example 8
Example 9
Example 10
Example 11
Example 12
Example 13
Example 14
Example 15
Example 16
Example 17
Example 18
Example 19
Example 20
Example 21
Example 22
Example 23
Example 24
Example 25
Hopefully I don't need more examples to show that this is very common.
While these examples are purely about
privacy.resistfingerprinting
, other settings that are suggested to be toggled off also have an either barely noticeable warning (only applicable to WebRTC) or none at all (basically every other tweak).For example,
webgl.disabled
breaks plenty of websites that use WebGL, with no warning. Togglingmedia.gmp-widevinecdm.enabled
breaks Netflix, Spotify, and other websites, with no real warning. Togglingmedia.eme.enabled
also breaks Netflix, Spotify, and other websites, with no real warning.And no, having a tiny description about what the setting does isn't enough. Those warnings really expect the user to either take the time to click "Details" or know what DRM/WebGL/etc. is. Instead, there should be a clear and easy to understand advisory about these settings.
My connection with the software
I guess my connection with Firefox is that I'm generally pretty involved in its community (frankly, as a fanboy) and hate to see that so many people are running into issues with Firefox for following settings on PTIO (again, that's not their fault as there aren't really any warnings for toggling these tweaks). Issues arising from following these settings reflect badly on the suggested software (Firefox) and makes people frustrated and less likely to care about privacy. I like PTIO generally but I think this is a huge issue that should be fixed sooner rather than later.
I know that section is and has been under a needed update which will probably take a lot of time until it is finished, but maybe adding this will not be much of an issue before that happens?
This can be dealt with in #1257 @dngray