alternative_right shares a report from 404 Media: An independent privacy audit of Microsoft, Meta, and Google web traffic in California found that the companies may be violating state regulations and racking up billions in fines. According to the audit from privacy search engine webXray, 55 percent ...
  • Pika@sh.itjust.worksEnglish
    3·
    15 days ago

    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 < 4 middle being < 12 high anything else)
    • any hardware characteristics(such as gyro, battery state, etc) -> 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.

    • FineCoatMummy@sh.itjust.worksEnglish
      1·
      15 days ago

      its just getting vendors to actually do it.

      Good ideas… and yeah… the browser vendors have a financial incentive to build mechanisms to collect anything and everything. Javascript itself exposes so much more fingerprinting possibilies.

      That’s also why I think it’s so terrible for Google’s Chrome to have like practically all the market share. G can now drive the whole web in a way that’s good for them and bad for us.