Honestly. I think if tracking is disabled it should do the following:

  • anything screen dimension related including available height/width -> blocked (realistically java-script should never need to disclose this information outside of an internal function anyway)
  • User Agent: generalized (this usually already is the case)
  • Cookie status: kept the same as needed for functionality.
  • addon/plugin info: blocked
  • buildID: blocked
  • hardware concurrently: generalized instead of a set number (low end being request for permission by default

Like there are many steps that can be done to help mitigate fingerprinting, its just getting vendors to actually do it.

being said I had never known about the TLS fingerprinting option, I generally don’t see that shown on the fingerprint detector sites, that’s interesting.