Live data from Hacker News

Firefox about:config privacy settings

gist.github.com

11–20 of 154 posts

Re: Firefox about:config privacy settings

#12
Some of these are strange choices and conflict. For example, disabling caching and then changing the cache size. Or disabling caching at all since it will have a significant negative performance impact. If you're concerned about what caching leaves behind use memory caching only.

Re: Firefox about:config privacy settings

#13
post #5

> dom.event.contextmenu.enabled = false This is a blunt tool. Some sites uses context menu events in a benign way. A better alternative is to simply bypass context handlers with shift-rightclick when necessary. > webgl.force-enabled This isn't really a performance improvement. If webgl is disabled it's due to troublesome drivers. Forcing it on can crash things. > layers.offmainthreadcomposition.enabled = true > layer…

Hey I didn't know about shift-rightclick. For me, disabling dom.event.contextmenu.enabled gives me both menus at once, then I tap Alt to get rid of the browser's menu if I want to use the app's menu underneath it. But I won't have to do that anymore.

Re: Firefox about:config privacy settings

#14
If you're interested in hardening your Firefox profile, check out this repository of user.js settings:

https://github.com/pyllyukko/user.js

This does things like blocking analytics and browser fingerprinting, and it's a simple to install or revert---just drop the user.js file in your Firefox profile directory.

Re: Firefox about:config privacy settings

#15
I noticed recently that unless I manually went in and set a master password, anyone can easily go into the FireFox settings and view all saved passwords..

I've been using FireFox Quantum as my primary browser for 3 or 4 months now and am really trying to love it, but chrome is just so much snappier..

Re: Firefox about:config privacy settings

#16
One thing that's frustrated me about FF (and kept me using Chrome) is that local development is a pain in general... for example, when I type `localhost` in my nav bar, Chrome autofills the port; FF doesn't (it just puts `localhost/`, which is useless). Next, FF interacts oddly with NGINX, telling me `The plain HTTP request was sent to HTTPS port`, whereas Chrome just passes me right along, giving me a little `Not Secure` text next to the URL.

Given I have to go to this website about 1000x per day, you can see why using FF is painful...

Anyone have any advice (on config, for example) for fixing this? And if anyone on the FF team is listening... I'd like to use your browser, but this has kept me from doing so.

Re: Firefox about:config privacy settings

#18
post #8

I don't like encouraging mucking around in about:config, but I might as well mention this one. If you don't mind your window losing vibrancy and rounded corners, you should be able to significantly improve battery life on macOS by setting "gfx.compositor.glcontext.opaque" to true. This makes WindowServer stop drawing whatever is behind the Firefox window. This bug tracks the proper solution: https://bugzilla.mozilla.…

I have a new 2018 MBP with an i9. I've noticed I can squeeze upwards of six hours battery out of it using Safari. With Firefox I'm lucky to get three.

I made this change just to see. So far it does appear to have lowered the energy impact score a bit, but I'm not sure it's enough to matter yet. I guess we'll know in a couple hours.

Edit: 20 minutes in and I've watched my Time Remaining estimate creep up from 3 hours to 5.5 hours. Seems like a solid win so far (other than it looks like crap).

Re: Firefox about:config privacy settings

#19

It makes me sad that a lot of the privacy are as damaging as the thing you are trying to avoid for no reason. Examples: - With right clicks I want sites to be able to supplement options but the only options are "complete replacement" or "no modification at all". - I don't want to disable sending MIME information when I paste to prevent a site from being able to block me from copying. - Why do I have to make the url u…

For the first one, just leave it on and use shift+rclick to bypass site handling of right click.

Re: Firefox about:config privacy settings

#20

One thing that's frustrated me about FF (and kept me using Chrome) is that local development is a pain in general... for example, when I type `localhost` in my nav bar, Chrome autofills the port; FF doesn't (it just puts `localhost/`, which is useless). Next, FF interacts oddly with NGINX, telling me `The plain HTTP request was sent to HTTPS port`, whereas Chrome just passes me right along, giving me a little `Not Se…

What port? If I

    $ sudo python -m SimpleHTTPServer 80
Then type localhost into the firefox url bar, I get the directory listing
Post reply on HN