this post was submitted on 14 Jul 2024
180 points (95.5% liked)

Privacy

31783 readers
571 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

I prefer Librewolf as it is easier and simpler to use

you are viewing a single comment's thread
view the rest of the comments
[–] MrOtherGuy@lemmy.world 2 points 3 months ago (13 children)

In addition, if you use user.js then you essentially cannot change those settings at runtime (via about:config or otherwise), because your user.js will override the settings on next startup. Maybe that's desired for some, but good to keep in mind nonetheless.

[–] kadotux@sopuli.xyz 4 points 3 months ago (7 children)

There's the provided user-overrides.js that's meant to do this

[–] MrOtherGuy@lemmy.world 1 points 3 months ago (6 children)

I don't think that could work. Not unless we are talking about different things, or unless you run their updater script everytime before starting Firefox.

[–] Shredder1750@lemmy.ml 1 points 3 months ago (1 children)

If you use user-overrides.js, it adds your custom preferences at the bottom of the user.js, as the prefs are read from top to bottom, if a new duplicate exist in your user-overrides.js but with a different value the new value would be used as it is at the bottom.

[–] MrOtherGuy@lemmy.world 1 points 3 months ago (1 children)

Yes, but that is not what I'm talking about. What I mean is that when Firefox is running and you go to change some setting in say, Settings page, then the new value for that preference is stored into prefs.js (at latest on Firefox shutdown, it might remain only in-memory for some time I'm not sure). Anyway, the new value persists only for that browser session, because on next startup whatever value was set by user.js will override it.

[–] laughterlaughter@lemmy.world 1 points 3 months ago (1 children)

Have you independently confirmed this?

What is preventing user.js from doing exactly what you're describing right now on your system?

[–] MrOtherGuy@lemmy.world 2 points 3 months ago (1 children)

Sure. For simplified example have only the following in your user.js file:

user_pref("browser.tabs.warnOnClose",true);
  1. Start Firefox
  2. Observe that the pref is indeed true
  3. Go to Setting > General, observe that Confirm before closing multiple tabs is checked
  4. Uncheck the option
  5. In about:config observe that browser.tabs.warnOnClose is now false
  6. Restart Firefox
  7. Observe that the pref is again set to true

The reason is also very simple. Firefox will never write anything to user.js - thus any changes you do at runtime will only be stored to prefs.js. However, user.js always overrides prefs.js at startup.

[–] laughterlaughter@lemmy.world 1 points 3 months ago* (last edited 3 months ago) (1 children)

Understood, thanks. So on a clean install, I'm assuming user.js is either empty or missing, correct?

[–] MrOtherGuy@lemmy.world 2 points 3 months ago

Yes. Firefox doesn't create user.js file itself - if you want one then you need to create it yourself either manually or with some tool. Also, I've seen some "security" software create user.js file without notifying the user about it...

load more comments (4 replies)
load more comments (4 replies)
load more comments (9 replies)