3 ms·
From the spec (https://github.com/WICG/compression-dictionary-transport#fingerprinting https://github.com/WICG/compression-dictionary-transport#fin...): > The
by pimterry 3y ago
From the spec (https://github.com/WICG/compression-dictionary-transport#fingerprinting https://github.com/WICG/compression-dictionary-transport#fin...):
> The existence of a dictionary is effectively a cookie for any requests that match it and should be treated as such:
> * Storage partitioning for dictionary resource metadata should be at least as restrictive as for cookies.
> * Dictionary entries (or at least the metadata) should be cleared any time cookies are cleared.
Given that, I think it offers no more client tracking possibilities than any other existing web tech (cookies, local storage, etc)..
- TonyTrapp 3y agoMaybe no more possibilities than regular cookies, but more stealthy for sure. Cookies are (somewhat) easily reviewable by the user through the web developer UI of most browsers; I doubt there will be any browser UI to managing compression dictionary.