• Artyom@lemm.ee
      link
      fedilink
      English
      arrow-up
      12
      ·
      6 months ago

      In my experience, you have thee choices. You can use NoScript and avoid enabling domains required for fingerprinting, you can turn on privacy.resistFingerprinting in about:config, or instead of focusing on not being fingerprinted, focus on guaranteeing your fingerprint will keep changing.

      • astreus@lemmy.ml
        link
        fedilink
        English
        arrow-up
        10
        ·
        6 months ago

        I turned privacy.resistFingerprinting to true and now get an absolutely unique fingerprint on the tool

        • Artyom@lemm.ee
          link
          fedilink
          English
          arrow-up
          8
          ·
          edit-2
          6 months ago

          That might be because it’ll be new every time.

          Edit: I haven’t done my homework about how good this post’s test is, but I use amiunique.org to compare browser settings.

        • PumaStoleMyBluff@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          6 months ago

          Be aware that any sites using HTML5 Canvas will probably be broken now. It breaks some other niche things too that may not be obviously related, so just keep that in mind if any site starts acting up.

      • Cryophilia@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        2
        ·
        6 months ago

        Funny thing is, I had to enable scripts on that website in order for the test to work lol

      • Corhen@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        6 months ago

        similar, i used Random User Agent, it shows that i have a unique finger print… but the user agent of that fingerprint is not ‘my’ user agent, so in 30 mintutes i would appear as a different fingerprint