Urgent.News

What's breaking now, across thousands of outlets.

Tech

about:config Settings Worth Changing (and What Not to Touch)

about:config is Firefox's advanced settings panel — a flat key-value store for hundreds of internal preferences. Most users never touch it. Knowing a handful of settings meaningfully improves privacy and performance. Accessing about:config Type about:config in the address bar → Accept the warning → Search for settings. Every setting has: A name (e.g., network.trr.mode ) A type (boolean, integer,…

about:config is Firefox's advanced settings panel, containing hundreds of internal preferences. Most users never modify it. However, tweaking a few settings can significantly enhance privacy and performance. To access about:config, type the phrase into your browser's address bar, accept the warning, and then search for the desired settings.

Each setting has a name, type, status, and value. Boolean settings toggle with a double-click, while integer and string settings allow editing upon a double-click.

Some settings worth considering are:

1. DNS over HTTPS (Forced Mode): network.trr.mode = 3 forces all DNS queries through your DoH resolver. Use this only if your resolver is reliable. You can set your preferred resolver using network.trr.uri = https://<resolver>/dns-query. Alternatives include Quad9, NextDNS, or AdGuard.

2. Encrypted Client Hello (ECH): network.dns.echconfig.enabled = true and network.dns.http3_echconfig.enabled = true encrypt the SNI in TLS handshakes. This protects your visited hostnames from passive observers on Cloudflare-hosted sites.

3. WebRTC Local IP Leaks prevention: media.peerconnection.ice.no_host = true prevents WebRTC from revealing your local network IP addresses while still allowing video calls via relay.

4. Fingerprinting resistance: privacy.fingerprintingProtection = true, privacy.resistFingerprinting = true (Firefox 117+) standardize browser properties, making your browser less identifiable. However, privacy.resistFingerprinting can break some sites, so privacy.fingerprintingProtection may be a better option.

5. Sanitize History on Shutdown: privacy.sanitize.sanitizeOnShutdown = true and privacy.clearOnShutdown.cookies = true privacy.clearOnShutdown.history = true clear cookies and history when Firefox closes. This is useful for shared computers or high-privacy profiles.

Some settings NOT worth changing include javascript.enabled = false, network.http.sendRefererHeader = 0, and network.http.pipelining = true. These changes can break essential functionality or provide minimal privacy benefits. Instead, consider using a user.js file or the Arkenfox user.js project to apply your preferred settings automatically on Firefox startup. Always back up your current settings before making changes and be cautious when experimenting with about:config.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Setting an env var above your imports does not run before them, and our integration test works anyway

The largest test file in PubTrivia is 543 lines, and it has no mocks in it. It calls the actual server actions a player's phone calls, and the actual engine the host's buttons and our WebSocket server…

  • Lines above imports do not run before imports in ES modules
  • Import declarations are hoisted, evaluated before module execution
  • Async function disabling WebSocket notifications returns early with warning

Debugging Service Workers in Firefox: DevTools, about:debugging, and Common Issues

Service workers are a critical web platform feature — they enable offline capabilities, push notifications, and background sync. Firefox has full service worker support.

  • Firefox provides comprehensive support for service workers with DevTools and about:debugging
  • Common Firefox service worker issues: incorrect scope, registration errors, and HTTPS requirements

A memory benchmark draft with 17 axes and no headline number: is it worth running?

I work at a company that builds memory infrastructure, so I'm biased: we compete in the thing this benchmark measures. We wrote a long-term memory benchmark called glasshouse, and I'd like to know if…

  • Glasshouse is a memory benchmark with 17 separate axes, each reported individually.
  • Benchmark includes 2,847 questions, 1.97 million tokens, and 50 photographs in 10 languages.
  • Creator invites others to run the draft benchmark on their own memory systems.

More from Friday 16 October →