https://addons.mozilla.org/firefox/addon/text-link/ - doubleclick plaintext link to use
|Firefox Multi Account Containers||Firefox Add-ons||TBD|
Firefox language packs
|Bitwarden||Firefox Add-ons||Chrome Web Store||TBD|
- Behave! - reveals portscanning performed by websites (detects IPFS).
- [HTTPS Everywhere], [source code]
- NoScript (which I use more for anti-annoyance than privacy)
- Snowflake to help censored users (won’t increase user privacy), requires WebRTC
- Firefox: IPvFoo
- Firefox: RSS feed preview
- Firefox: IPFS Companion
- Firefox: beta channel of IPFS Companion
- doesn’t sync automatically with Firefox Sync.
- At the time of writing, 2019-07-13, I consider IPFS as incompatible with Tor Browser as Tor browser would use the local IPFS daemon, which is not using Tor and thus the IPFS network could see your real IP especially if not many nodes are requesting the fetched content.
- Firefox: beta channel of IPFS Companion
- Firefox: Foxy Proxy
- Firefox: Foxy Tab
- Verify-Me for rel=me verifications (Indieweb)
- Firefox: Tree Style Tab
- Tab Suspender
- Dark Background and light text (GitHub)
- Invdition - YouTube to Invidious and Twitter to Nitter
TODO: Sort this list.
truefor preventing domains from accessing each other’s data.
falseto stop sponsored links.
trueto force HTTPS and not need HTTPS Everywhere
falsein order to not trust system CA store in case of enterprise MITM
truein order to not allow OCSP soft fail. I am not sure if this is a good idea.
trueso letterboxing is used to hide real browser size. Tor Browser support
`extensions.pocket.enabled` to `false` so the Pocket integration goes away
- On Linux
widget.content.gtk-theme-override(a string that has to be created by user) to
Adwaita:lightso text boxes in dark themes become readable, thank you Dovydas Venckus
oncein order to have gifs play once and then stop everywhere (
noneto never have them play).
https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%in order to send nearby WiFi networks to Mozilla instead of Google. See also MLS Software.
`media.peerconnection.enabled` to `false` in order to disable WebRTC (potential IP leaker, will break VoIP/calls, but those are better outside of Firefox anyway)
Not needed anymore in 2020, WebRTC has improved to not do that.
falsein order to also hide cameras and microphones from websites. I am not sure if this is still necessary either, but maybe it will remind me that I have focused my VoIP to Chromium?
truein order to enable HTTP/3 / QUIC support. It can be confirmed working in
truein order to see punycode instead of UTF-8 in case of spoofing attempt. However makes reading non-ASCII domains painful.
truein order to allow reader use to be used on ~all websites and devices (regardless of low RAM?)
toolkit.telemetry.serverto empty in order to not send telemetry (which may be blocked by filtering DNS providers such as AdGuard or NextDNS resulting high amount of failing queries)
DNS over HTTPS
network.trr.bootstrapAddressDNS server to use for resolving the DoH name, e.g.
184.108.40.206(Resolver 2 of Quad9)
network.trr.modedepends, 2 to prefer DoH, but fallback to system resolver (or 3 to enforce DoH without fallback). If there is system encrypted DNS, just take 5 to at least benefit from the system DNS cache.
- DoH is required by Firefox ESNI support which encrypts SNI which would still leak which sites you visit. Another bug about ESNI + Android DoT
- I have ended up to recommending 2 as otherwise the DoH server going
down stops DNS from working on your Firefox entirely, which may be
more of a problem than unencrypted SNI as not everyone supports it.
- since then I have decided that 5 is the best option, because otherwise it goes past my Unbound setup. I hope Mozilla/Firefox will fix the two bugs linked above, so I don’t have to choose between DNS under my control vs encrypted SNI.
trueto hopefully prefer IPv6
network.trr.urifor the actual resolver address, e.g.
https://220.127.116.11/dns-query(removes the need for
3?) or Privacy Guides list of Encrypted DNS Resolvers
- You can confirm TRR working by visiting
about:networking#dnswhere you should be seeing DNS cache of Firefox and a lot of
- Quad9 became my preferred resolver through anxiety about other options being small (and possibly more likely to go down) or commercial while Quad9 is non-profit organization and 2019-03-20 apparently the default fallback resolver of dnscrypt-proxy (at least in Debian).
- Quad9 while having filtering of malicious domains should be easy to figure out as the problem if something doesn’t work on my computers as due to the previously mentioned bug I am mainly using it on Firefox.
- While investingating how Android 9 Private DNS works, I also wrote a DNS provider comparsion here
This information is from Arch Wiki on Firefox tweaks
falseto only cache to RAM.
truewhich should be default)
600000in order to only store open session every ten minutes (instead of 15 seconds) in case of crashes.
falseto not store the session data for crash recovery at all. I think this may be the more healthy option with all the information flood and dozens of tabs.
Every object loaded (html page, jpeg image, css stylesheet, gif banner) is saved in the Firefox cache for future use without the need to download it again. It is estimated that only a fraction of these objects will be reused, usually about 30%. This because of very short object expiration time, updates or simply user behavior (loading new pages instead of returning to the ones already visited). The Firefox cache is divided into memory and disk cache and the latter results in frequent disk writes: newly loaded objects are written to memory and older objects are removed.
Firefox stores the current session status (opened urls, cookies, history and form data) to the disk on a regular basis. It is used to recover a previous session in case of crash. The default setting is to save the session every 15 seconds, resulting in frequent disk access.
and this is the reason why Firefox is at times accused of killing SSDs.
|Changelog: GitHub.com commits||gitea.blesmrt.net commits|