31–40 of 89 posts
I'd recommend to read these notes of Firefox config: https://www.privacytools.io/#about_config
It might be difficult to read, but there a little bit more information and links which aim to protect privacy.
Earlier quoted context omitted.
I used to run Firefox with resist fingerprinting enabled. I believe it was causing chat time stamps on websites like WhatsApp to be incorrect, which was annoying but I don’t know if you consider that broken.
Yes I discovered that when viewing the TV guide on plex. Everything was an hour out (UK). I think with resist fingerprinting the timezone is set to UTC0. In the end I had to turn that setting off.
Earlier quoted context omitted.
I won't ask for a complete audit, but is there one example from the wizard that could break stuff, that is NOT called out by the wizard itself?
That might be true for a technical user, but is the average user going to know that discord is broken because they disabled webrtc? Also, resistfingerprinting is going to significantly increase the difficulty of recaptcha challenges you encounter.
I wish Firefox exposed a better UI for it's profiles. It seems like a really powerful feature that is much less useful than it might be due to poor ergonomics...
That's something that I like about experiments in "Container Tabs", where you get the power of separate profiles, but the ability to mix-and-match them in the same browser window and opening a profile can be as simple as opening a new tab. I understand though why Mozilla seems to be having such a hard time converging on a UX for Container Tabs that makes everyone happy and it may be impossible to ever surface 100% of…
Earlier quoted context omitted.
That might be true for a technical user, but is the average user going to know that discord is broken because they disabled webrtc? Also, resistfingerprinting is going to significantly increase the difficulty of recaptcha challenges you encounter.
ResistFingerprinting is currently known to break Google's Recaptcha v3. Here is the Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1503872
Earlier quoted context omitted.
Maybe Mozilla should remove about:config, so users can't hurt themselves on it. I'm sure the telemetry shows its rarely used, and when it is, it often breaks the browser in ways that are unfixable for the average user. Malware is also able to modify these advanced settings to hijack the browser in nasty ways, and slow down Firefox, and make people switch to Chrome faster. If they don't remove it Firefox is going to c…
>(This is in fact sarcasm before you get too eager with that down arrow) I see this defense quite a lot on the internet, and I think it's misplaced. Even without your comment, I would have downvoted you, not because I though you were in earnest, but because your sarcastic comment doesn't add anything to the conversation.
Earlier quoted context omitted.
I used to run Firefox with resist fingerprinting enabled. I believe it was causing chat time stamps on websites like WhatsApp to be incorrect, which was annoying but I don’t know if you consider that broken.
It also breaks add-on compatibility because it sets your user agent to the last ESR version of Firefox, which may be several versions behind the version you're actually running.
I feel the strong need to point out some of these settings will break Firefox in subtle and hard to understand ways. There’s a reason you “void the warranty” when tweaking the about:config preferences. No rule against it, but just watch out. (Mozilla employee)
This used to be impossible, and essentially made my employer banish Firefox in most cases.