rowan_m

14 ms·

1.
by rowan_m 7y ago
This is a staged rollout with Chrome 80 as announced, so any current plans you're making for this change should stay as is. If you're looking to know if your specific browser instance is enforcing the new behaviour you can check
2.
by rowan_m 7y ago
This is part of what the Privacy Budget ( https://github.com/bslassey/privacy-budget ) proposal aims to tackle. Freezing the User-Agent string reduces the amount of information exposed by default. UA Client Hints means t
3.
by rowan_m 7y ago
> With this new standard, just ask the user agent to include all details in its Accept-CH header. That becomes an explicit choice by the site to request more information, it's up to the client/browser how it responds to that. F
4.
by rowan_m 7y ago
Client Hints ( https://wicg.github.io/ua-client-hints/ ) move a passive fingerprinting vector to an active one, i.e. information must be explicitly requested by the site and then the browser can choose how to respond. Th
5.
by rowan_m 7y ago
It changes the passive fingerprinting vector to an active one: https://github.com/bslassey/privacy-budget#passive-surfaces So, while UA hints could potentially supply more information than the current UA string - each
6.
by rowan_m 7y ago
For older browsers, the UA string remains - so that's still viable for compatibility issues. https://wicg.github.io/ua-client-hints/ will provide the cleaner, opt-in approach in the future.
7.
by rowan_m 7y ago
Correct, in that I think of a "Site" as an entity defined a layer above the "Domain". However the "Domain" attribute and the "SameSite" attribute control different behaviour. "SameSite" affe
8.
by rowan_m 7y ago
Users often get apps installed for them by the store at purchase. So, while they may have 3p apps installed it's not necessarily a good signal they will install more.