K4sum1 Posted August 24, 2024 Author Posted August 24, 2024 Mozilla devs do not revert changes unless it breaks building the browser. Even if the change sucks and nobody likes it.
D.Draker Posted August 24, 2024 Posted August 24, 2024 11 hours ago, K4sum1 said: Mozilla devs do not revert changes unless it breaks building the browser. Even if the change sucks and nobody likes it. Wow! Thanks for the info! So, modding CentBrowser, then?
K4sum1 Posted August 24, 2024 Author Posted August 24, 2024 idk anything about Chromium, that includes CentBrowser.
D.Draker Posted August 24, 2024 Posted August 24, 2024 15 hours ago, K4sum1 said: idk anything about Chromium, that includes CentBrowser. I'll help with what I can, starting with, did you apply the fix for the well known bug? # SSL selfsigned fix security.enterprise_roots.enabled=true
D.Draker Posted August 24, 2024 Posted August 24, 2024 app.update.auto.migrated=false app.update.auto=false app.update.badge=false app.update.channel="" app.update.checkInstallTime=false app.update.enabled=false app.update.mode=0 app.update.service.enabled=false app.update.silent=false app.update.staging.enabled=false
K4sum1 Posted August 25, 2024 Author Posted August 25, 2024 On 8/24/2024 at 2:15 AM, D.Draker said: security.enterprise_roots.enabled=true I assume Mozilla has a reason to not enable this by default. It's not telemetry or anything malicious. The update stuff does not matter here since the updater component is disabled at compile.
D.Draker Posted August 25, 2024 Posted August 25, 2024 accessibility.force_disabled=true app.shield.optoutstudies.enabled=false beacon.enabled=false browser.laterrun.enabled=false browser.shell.checkDefaultBrowser=false
D.Draker Posted August 25, 2024 Posted August 25, 2024 browser.slowStartup.notificationDisabled=true browser.uitour.enabled=false
D.Draker Posted August 25, 2024 Posted August 25, 2024 Found more, use what you like. default-browser-agent.enabled=false extensions.update.enabled=false extensions.update.autoUpdateDefault=false
D.Draker Posted August 25, 2024 Posted August 25, 2024 Rendering tweaks. layers.deaa.enabled=false gfx.canvas.skiagl.dynamic-cache=false gfx.work-around-driver-bugs=false
D.Draker Posted August 25, 2024 Posted August 25, 2024 On 8/25/2024 at 3:17 AM, K4sum1 said: I assume Mozilla has a reason to not enable this by default. It's not telemetry or anything malicious. Yes, I know it's not telemetry, it's a bug that doesn't recognise legit self-signed certs, plenty of info about that, but then again, use what you like.
K4sum1 Posted August 26, 2024 Author Posted August 26, 2024 7 hours ago, D.Draker said: accessibility.force_disabled=true app.shield.optoutstudies.enabled=false beacon.enabled=false browser.laterrun.enabled=false browser.shell.checkDefaultBrowser=false accessibility.force_disabled I build with ac_add_options --disable-accessibility, so not applicable here. app.shield.optoutstudies.enabled is already set to false. beacon.enabled is still true since it seems to be a web standard, and I don't want to break anything that may use it. However if it is bad let me know. browser.laterrun.enabled is already set to false. browser.shell.checkDefaultBrowser I want to keep at true because I don't want to confuse new users if they want to set as default and are used to the prompt. 7 hours ago, D.Draker said: browser.slowStartup.notificationDisabled=true browser.uitour.enabled=false browser.slowStartup.notificationDisabled has no mention in the Firefox source code, so would be useless to set. browser.uitour.enabled again seems like something that could confuse new users if disabled, so I'd rather keep it on. 3 hours ago, D.Draker said: default-browser-agent.enabled=false extensions.update.enabled=false extensions.update.autoUpdateDefault=false default-browser-agent.enabled I build with ac_add_options --disable-default-browser-agent, so not applicable here. extensions.update.* Automatic extension updates are fine, some just need to update like uBlock Origin with everything YouTube is trying to do. 3 hours ago, D.Draker said: layers.deaa.enabled=false gfx.canvas.skiagl.dynamic-cache=false gfx.work-around-driver-bugs=false I'd rather not mess with rendering stuffs and anger people if the defaults work fine for most.
Mathwiz Posted August 26, 2024 Posted August 26, 2024 I think the captive portal detection is pretty harmless, but TBH, it's also unnecessary for a desktop PC. Might be useful for laptops that get taken to hotels, restaurants, and the like. So I'd disable it on my desktop PC or a laptop that never goes anywhere, like my work PC, but I wouldn't stress too much over it accidentally being left enabled either. All it's doing it making a connection to a known site and seeing if it gets the expected response. If it doesn't, there must be a captive portal in the way. I suppose you could consider that "telemetry" but it's pretty darn minimal - all Mozilla knows is that you started their browser (along with the OS and browser version from the user agent, which you could spoof if you wanted to mess with them - tell them your running FF 129 on Win XP and let them scratch their heads!) And yes, they'll know your IP - but any site you connect to will know your IP unless you're using a VPN or external proxy. 1
Mathwiz Posted August 26, 2024 Posted August 26, 2024 24 minutes ago, K4sum1 said: beacon.enabled is still true since it seems to be a web standard, and I don't want to break anything that may use it. Beacon lets sites know when you leave a Web page. It's disabled in Serpent, so I think it's safe to disable in r3dfox, but users beware: there are ways to accomplish the same task via Javascript, so don't be fooled into thinking you're protected from this sort of snooping just because beacon is disabled. 1
Guest Posted September 3, 2024 Posted September 3, 2024 (edited) ********** Edited September 4, 2024 by Sampei.Nihira
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now