|
@mikewest | |||||
|
I'm excited about this. The UA string is a mess, somewhat fingerprintable, and legitimate use cases can be better and more clearly served by moving the information to an HTTPS-only client hint (a la wicg.github.io/ua-client-hint…). twitter.com/intenttoship/s…
|
||||||
|
||||||
|
Mike Sherov (he/him) 🚀
@mikesherov
|
14. sij |
|
Would a partial UA freeze accomplish the same thing without the ecosystem churn? And what are plans to address the "first visit" problem? "Client Hints Preload List"?
|
||
|
|
||
|
Mike West
@mikewest
|
14. sij |
|
A partial freeze wouldn't flip UA information from on-by-default to opt-in. I think the client hint infrastructure is the right way to make this data available to servers. Likewise, the first visit problem is one that CH needs to address generally. @yoavweiss has ideas.
|
||
|
|
||
|
Steven Roussey
@sroussey
|
14. sij |
|
The rest of google is going to hate this. No one browser sniffs via UA more than Google.
|
||
|
|
||
|
Mike West
@mikewest
|
14. sij |
|
Google is large, it contains multitudes. I'm pretty sure some folks will be less excited about this change than I am. :)
|
||
|
|
||
|
Aram Zucker-Scharff
@Chronotope
|
14. sij |
|
Cool! What's the schedule for UA-CH to be testable as-proposed in Canary?
|
||
|
|
||
|
User-ISNUK 👀
@DerNivel
|
15. sij |
|
Didn't Google change from Inc. to LLC some years ago? Just asking because the draft is mentioning "Google Inc."
|
||
|
|
||
|
Huuuze
@Huuuze
|
25. sij |
|
If I'm understanding this correctly, will users be given browser options that allow them to _decide_ what they share with a website?
|
||
|
|
||
|
D34TH0FKVorshk
@D34TH0FKVorshk
|
15. sij |
|
just another attempt by google to consolidate power over the web. god I cant wait to get my Open source phone.
|
||
|
|
||