21–30 of 154 posts
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..
what are the reasons for disabling memory and disk cache, and lowering dns caching?
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.…
One issue fudging around with about:config presents could be increased fingerprintability. More battery life is cool, but will it come at the expense of an easily fingerprinted browser profile?
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
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…
One small change I made was streaming music to my phone, and that had a big impact.
I know that streaming will use some battery life, but the amount of CPU being used by say, Pandora, was rather extreme.
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 don't like encouraging mucking around in about:config, but I might as well mention this one. One issue fudging around with about:config presents could be increased fingerprintability. More battery life is cool, but will it come at the expense of an easily fingerprinted browser profile?
I frequently see recommendations to disable "safe browsing" features. Why?
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
Earlier quoted context omitted.
What port? If I $ sudo python -m SimpleHTTPServer 80 Then type localhost into the firefox url bar, I get the directory listing
It must be a different port, otherwise localhost without a port number would work fine. Presumably 8080 or something, which is common for user apps to use since without privileges you can't open a port below 1024 normally.
Chrome doesnt do this either as far as I can tell.