|
|
|
|
|
by ulan
2253 days ago
|
|
Author here. Fingerprinting is a valid concern. The API explainer has a section about it:
https://github.com/WICG/performance-measure-memory#fingerpri... It is important to keep in mind that the API only accounts for the objects allocated by the web page itself and does not expose the total memory usage of the browser. The only information that can be extracted using the API is the browser version (because an object representation may change between different versions) and the bitness of the browser (32-bit vs 64-bit). This information is already exposed by other existing APIs (e.g navigator.userAgent, navigator.deviceMemory) Thus the API does not add _new_ data bits for tracking. The final spec of the API may include additional protection against fingerprinting. For example, adding a small amount of Gaussian noise would make browser version inference much more difficult. |
|