• 7heo@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    7 months ago

    Yeah, make your user agent absolutely unique. Too much entropy will surely confuse the shit out server side HTTP Header tracking. 😬

      • 7heo@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        7 months ago

        Oh gee, I wasn’t aware there was more to it than the UA. Thanks for opening my eyes.

        Edit: I checked your link, most of the parameters on the test require client side execution. That (client side tracking) is absolutely unrelated to what (server side tracking) I was talking about, and is something you can control (by not allowing JavaScript, for example). Please do not confuse the two. There is literally nothing you can do against server side tracking.

    • Rentlar@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      Yeah this isn’t my UA but I’m just saying these parts are what’s considered the supported featureset rather than information about what software the device is running.

      • 7heo@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        Yes, I get that point, but I also think that it’s tempting for the privacy-minded novice to think “the less information I provide, the better!”, while in actuality, it is better to provide “more” information: the most common UA, even if it means lying about your featureset. In this case, truly, more is less.