3 ms·

New browser APIs generally take privacy and fingerprinting concerns into account. This one too: https://web.dev/multi-screen-window-placement/#security-and-perm

• 0xy 6y ago
  Audio APIs were released as recently as last year that are used for widespread fingerprinting via audio hardware latency information that is available with no notice to the user and without their permission, even on websites with zero audio. This simply isn't true. That's not even the only recent API that Chrome has spearheaded that is being abused by ad networks and other nefarious actors.
  • gruez 6y ago
    > Audio APIs were released as recently as last year that are used for widespread fingerprinting via audio hardware latency information that is available with no notice to the user and without their permission, even on websites with zero audio. That seems to be fixed, at least on firefox. The result from console.log(new AudioContext()) seems to be generic values that don't correspond to the actual values (eg. it reports the sample rate as 44.1khz, but my system sample rate is 48khz).
    • 0xy 6y ago
      None of what you said is relevant to Chrome. Chrome still allows ad networks to pilfer this information as of the latest version. Chrome is the worst browser for privacy by far. Between cookie policies, X-Client-Data backdoors for DoubleClick and APIs like this one it seems awfully convenient that this stuff continues to make it to production for ad networks to abuse with impunity.