new wiki

Actionable

• 1.1: explain “state”
  • additional link to a list of types of state
• 2.2: explain why (or drop) prefs.js is insufficient and a stupid idea
• 3.1, 3.4: don’t refer to “starting with Arkenfox v97”
• 3.2: “Cookies” options
  • use settings, not options
  • use hamburger menu symbol
  • show the two methods are either/or
• 3.2: be consistent with 'override this/these`: either do say it for all or say it for none
• 3.3: add pic/example of RFP canvas
• 3.5: add warning not to delete prefs.js
• ALL: excluding bullet points: sentences should end with a period
• ALL: add anchors so it’s easy to link to various bits
  • bold non-anchors subheaders to match style
• 4.1: Cookie Extensions API link is now a dead bugzilla (marked invalid)
  • misread that from one of the last comments. It was resolved in FF94
  • the point remains that APIs may be lacking to properly sanitize (which is what a previous iteration of the wiki said)
• 4.1: add pic for uBO add custom filter
• 4.1: add pic/info on Smart Referer whitelist
• 4.1: rework FPing extensions into a single don’t bother entry
• 5.1: update prefs in windows updater merge example
  • just dom.netinfo.enabled to go: am tracking this elsewhere
• 5.2: troubleshooting: DONE
• Appendix A: cleanup
• Appendix B: split FP test sites into a new wiki page
• Appendix B: add foreword = FPing tests that give entropy (or advice) are BS etc
  • I am tracking this elsewhere
• Appendix C: cleanup

---

it’s not complete

• I will be tidying up the 5 items
  • including #1350 to match
  • updater options to use generic pref names in examples

But for everything up to the 5’s - comments welcome

• is there anything that is missing
• is there anything that is not clear enough
• is there anything that can be removed
• should I add anchors to subtitles
• any fucked up links
• anything else

Speak now or forever hold your penis

[Thorin-Oakenpants]

https://github.com/arkenfox/user.js/commit/1ba6a21e4d9455445ffe26837f8bca57a92d11e3#diff-417e8f625f16252f8ace3b0791d24c9b073d7394e9216c7b5d14a516d2572277R459

exactly: if it’s a govt website or two that is always the issue and you need to use those sites all the time (because its the govt), then consider your secondary browser - everyone should have one

 * [SETUP-WEB] SSL_ERROR_UNSAFE_NEGOTIATION: is it worth overriding this for that one site

[GlassGruber]

If anyone of you can explain me where FF or Arkenfox wants to go in therms of anonymity, I would be happy:)

If you look at wiki 1.1 you can see this (bold is mine)

🟪 TOR BROWSER

If your threat model calls for anonymity and advanced fingerprinting protection, USE TOR BROWSER. You can also use Tor Browser for everyday browsing as another secondary browser. However, you’re going to want a non-Tor Browser browser too, which is Firefox, so carry on reading 😃.

But I would stress more on the most important part of this snippet

your threat model

It’s a very complicated and deep subject, but in my opinion IF you can’t really tell what a threat is to you, then potentially you can go on without much bothering about this thing, because AF and other tools mentioned in the wiki will take care of most common things for you.

If you look at the resources and links in the wiki, a lot about this subject can be found where you can surely get a grasp of what are possible threats for you and what you should care about and what not.