3 ms·

I believe main use of WebGPU, as well as WebGL will be fingerprinting therefore they should be put behing a permission. It is ridiculous that browser developers

I believe main use of WebGPU, as well as WebGL will be fingerprinting therefore they should be put behing a permission. It is ridiculous that browser developers do nothing to reduce API surface usable for fingerprinting and instead just extend it.

chrisjc 3y ago
While I don't disagree with the essence of what you're concerned about, I imagine that every new step/functionality in the browser evolution introduces new minutiae that can be used in fingerprinting. Also, once/if the WebGPU interface expands into more direct GPU functionality, I imagine there will many that will try to use your GPU for crypto mining/etc. But surely a permission option/prompt will eventually be introduced, but probably not by google in chrome. Anyone know the roadmap/timeline for WebGPU on Firefox and other browsers?
- codedokode 3y ago
  > I imagine that every new step/functionality in the browser evolution introduces new minutiae that can be used in fingerprinting. No problem; just put such APIs behind a permission and they become unusable for fingerprinting.
  - PoignardAzur 3y ago
    If you do that too much, you just train users to enable all permissions all the time without thinking.
  - astrange 3y ago
    If you can query for permission without a prompt appearing that's another data point.
nwoli 3y ago
People keep saying “webgpu will just be used for fingerprinting” here on HN as a meme constantly but it’s clearly not the case. There’s obvious use cases not involving finger printing for webgl, and webgpu has tons of convenience functions that makes it superior to webgl to make things nearly impossible otherwise (eg atomics to name just one)
overgard 3y ago
Kinda doubt it's that great for fingerprinting. Look at something like WebGL report and any semi-modern system will support everything. "Computer was made in the last 10 years" isn't that useful. Even knowing the exact GPU... we're talking maybe 5 major vendors? Seems like if you really care for anonymity you need a vpn and a special browser at this point anyway.

chrisjc 3y ago

While I don't disagree with the essence of what you're concerned about, I imagine that every new step/functionality in the browser evolution introduces new minutiae that can be used in fingerprinting. Also, once/if the WebGPU interface expands into more direct GPU functionality, I imagine there will many that will try to use your GPU for crypto mining/etc. But surely a permission option/prompt will eventually be introduced, but probably not by google in chrome. Anyone know the roadmap/timeline for WebGPU on Firefox and other browsers?

codedokode 3y ago
> I imagine that every new step/functionality in the browser evolution introduces new minutiae that can be used in fingerprinting. No problem; just put such APIs behind a permission and they become unusable for fingerprinting.
- PoignardAzur 3y ago
  If you do that too much, you just train users to enable all permissions all the time without thinking.
- astrange 3y ago
  If you can query for permission without a prompt appearing that's another data point.

nwoli 3y ago

People keep saying “webgpu will just be used for fingerprinting” here on HN as a meme constantly but it’s clearly not the case. There’s obvious use cases not involving finger printing for webgl, and webgpu has tons of convenience functions that makes it superior to webgl to make things nearly impossible otherwise (eg atomics to name just one)

overgard 3y ago

Kinda doubt it's that great for fingerprinting. Look at something like WebGL report and any semi-modern system will support everything. "Computer was made in the last 10 years" isn't that useful. Even knowing the exact GPU... we're talking maybe 5 major vendors? Seems like if you really care for anonymity you need a vpn and a special browser at this point anyway.