Thorin-Oakenpants 60db0ebac4
remove confusing comment
> serviceWorkers require an "Allow" permission

I made this change as part of v103 (after we finally migrated off lifetime cookie policy), but I cannot for the life of me work out why I mentioned SWers needing an allow permission - there is no such thing in ctrl-I or under privacy> permissions. (I checked ESR102, and current)

If anyone can enlighten me, speak up
2024-06-07 03:29:25 +00:00
2023-11-19 09:56:47 +00:00
2023-11-02 21:17:15 +00:00
2020-09-15 06:07:32 +00:00
2019-06-26 13:32:12 +00:00
2017-03-01 00:11:05 +02:00
2020-09-15 04:19:03 +00:00
2023-11-24 13:38:25 +00:00
2023-03-13 07:13:07 +00:00
2023-11-24 13:35:14 +00:00
2024-06-07 03:29:25 +00:00

🟪 user.js

A user.js is a configuration file that can control Firefox settings - for a more technical breakdown and explanation, you can read more in the wiki

🟩 the arkenfox user.js

License: MIT

The arkenfox user.js is a template which aims to provide as much privacy and enhanced security as possible, and to reduce tracking and fingerprinting as much as possible - while minimizing any loss of functionality and breakage (but it will happen).

Everyone, experts included, should at least read the wiki, as it contains important information regarding a few user.js settings. There is also an interactive current release, thanks to icpantsparti2.

Note that we do not recommend connecting over Tor on Firefox. Use the Tor Browser if your threat model calls for it, or for accessing hidden services.

Also be aware that the arkenfox user.js is made specifically for desktop Firefox. Using it as-is in other Gecko-based browsers can be counterproductive, especially in the Tor Browser.

🟧 sitemap

🟥 acknowledgments

Literally thousands of sources, references and suggestions. Many thanks, and much appreciated.

Description
Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening
Readme 11 MiB
Languages
JavaScript 72.2%
Shell 15.9%
Batchfile 11.9%