Getting Fingerprint Detector reports about high number of fingerprinting API calls on Programming.dev instance.

Is there a reason for that? Not getting it on others instances. Report

  • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Hate to be a party pooper but the API usage in that log looks completely normal for a PWA… You should be looking at the outgoing network data instead IMO

    Maybe one of the devs could advise better if you provide the frontend/client you’re using, and what page you are experiencing the issue on, as well as other instances where it isn’t happening

    • mirkl@programming.devOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      It happens on 1st page load, then PWA create a lot of cached data.

      It doesn’t happen on other lemmy instances, maybe some, but you can check for example lemmy.ml.

      You can check using JShelter Firefox addon. So basically application calls a lot of JS API calls to identify system capabilities even if they are not required by PWA. Results of such calls could be used to fingerprint your browser.

      Maybe it is some JS library that checks capabilities to load polyfills?

      vs

      • snowe@programming.devM
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Can you message me in a few days about this? I’m out of town and won’t have time to look into it for a least a few days but I really don’t like trackers and I’m not sure why programming.dev would have any trackers cuz I most definitely didn’t add them. (I run Firefox with ublock matrix, several other tracker prevention mechanisms including Firefox’s built in fingerprinting blocking, sometimes I switch to Orion which also has good tracking blocking).