Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox about:config privacy settings

gist.github.com

Post reply on HN
Print view View original

91–100 of 154 posts

Re: Firefox about:config privacy settings

#91

Post by markdog12 »

pcwalton wrote: 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.…

Sorry to hijack this thread, but I noticed in your presentation (can't find it now) you could test out pathfinder with --features=pathfinder on Firefox Nightly. Any way to tell if this really enables pathfinder? I ask because I can't tell a difference on Windows or Mac (which may mean it's working as intended).

https://github.com/pcwalton/pathfinder

Re: Firefox about:config privacy settings

#92

Post by sammoth »

saiya-jin wrote: post #66
phyzome wrote: post #60

This list is somewhere between worthless and dangerous. Chesterton's Fence: Presumably Mozilla has already optimized the privacy and performance of Firefox as much as they've felt comfortable doing. If they could change each of those settings as recommended without tradeoffs to help the user, they would have done so. Without listing the tradeoffs for each one, this list cannot be relied upon.

Yeah right, because me being forbidden to right click on the site is really in my best interest. I might, you know, inspect DOM and block annoying permanent menus or ads that ublock origin doesn't filter out. And being able to do copy&paste of the content should send me straight to prison.

You can hold shift while right clicking to get the normal menu anywhere that it is disabled/replaced

Re: Firefox about:config privacy settings

#93

Post by _8j50 »

Uplink wrote: post #81

Who do I tell my brand new, bright idea about IDN attack prevention? It goes like this: Display characters that are out of range of your selected language's character set in a different colour than the characters of your language. That way, when you go to раураӏ.com that last character shows up in red. Homework: select two languages (e.g. Chinese and English), and use three colours. Make the colour scheme colour-blin…

They're supposed to display in punycode characters outside of your locale.

Maybe whitelisting specific characters instead of only locale would be best.

Your color idea is neat but look at it from the perspective of people that actually use idn domains and don't speak english. What if раураӏ.com was раураӏ.fans-ùøê.com where ùøê was part of the same charset as ӏ and the user speaks both locale. Even if you color it,it would be difficult to train users to pick up on that.

Re: Firefox about:config privacy settings

#94

Post by Someone1234 »

krn wrote: post #83
phyzome wrote: post #60

This list is somewhere between worthless and dangerous. Chesterton's Fence: Presumably Mozilla has already optimized the privacy and performance of Firefox as much as they've felt comfortable doing. If they could change each of those settings as recommended without tradeoffs to help the user, they would have done so. Without listing the tradeoffs for each one, this list cannot be relied upon.

What Mozilla did in the default Firefox configuration, is made the trade-offs on behalf of an average browser user. It's neither worthless, nor dangerous for a savvy browser user to make the trade-offs for himself. That's exactly what software configurations are for.

That might be a good argument if the link was to an article with a large amount of discussion about the pros and cons of each configuration change, instead of just a list of changes with a brief overview of what they do.

Re: Firefox about:config privacy settings

#95

Post by krn »

Someone1234 wrote: post #94
krn wrote: post #83

Earlier quoted context omitted.

What Mozilla did in the default Firefox configuration, is made the trade-offs on behalf of an average browser user. It's neither worthless, nor dangerous for a savvy browser user to make the trade-offs for himself. That's exactly what software configurations are for.

That might be a good argument if the link was to an article with a large amount of discussion about the pros and cons of each configuration change, instead of just a list of changes with a brief overview of what they do.

As the one who posted this link here, I found the list to be a great starting point for my research. Instead of switching to something like Waterfox or Brave, I can now remain with a major web browser by just enabling the features I need.

Re: Firefox about:config privacy settings

#96

Post by xfer »

colecut wrote: post #80
nathancahill wrote: post #57

Earlier quoted context omitted.

Isn't that true for any browser though?

Chrome prompts me for my system password before letting me view passwords

Depends what system you are on? It might make use of libkeyring if available on linux for example, i prefer not to save passwords on browsers and use password managers.

Re: Firefox about:config privacy settings

#97

Post by muizelaar »

markdog12 wrote: post #91
pcwalton wrote: 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.…

Sorry to hijack this thread, but I noticed in your presentation (can't find it now) you could test out pathfinder with --features=pathfinder on Firefox Nightly. Any way to tell if this really enables pathfinder? I ask because I can't tell a difference on Windows or Mac (which may mean it's working as intended). https://github.com/pcwalton/pathfinder

pathfinder is not available in Nightly

Re: Firefox about:config privacy settings

#98

Post by gsnedders »

OzzyB wrote: post #85

Somewhat tangental but can someone explain why Firefox users need to explicitly enable new Streams API support? [1] Safari, Chrome implement these APIs out-of-the-box but FF wants users to open `about:config` (and ignore the ominous warning) and set `dom.streams.enabled` and `javascript.options.streams` to `true`. It seems a little backwards to me since this has been available since version 57 and their webpage is th…

Quality of implementation.

https://bugzilla.mozilla.org/show_bug.cgi?id=1389628 is the tracking bug for enabling it by default.

Re: Firefox about:config privacy settings

#99

Post by pcwalton »

markdog12 wrote: post #91
pcwalton wrote: 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.…

Sorry to hijack this thread, but I noticed in your presentation (can't find it now) you could test out pathfinder with --features=pathfinder on Firefox Nightly. Any way to tell if this really enables pathfinder? I ask because I can't tell a difference on Windows or Mac (which may mean it's working as intended). https://github.com/pcwalton/pathfinder

That's the Cargo feature used to build Pathfinder, not a nightly flag.
Post reply on HN