Page MenuHomePhabricator

Deal with Google Chrome User-Agent deprecation
Open, Needs TriagePublic

Description

Source: https://groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/-2JIRNMWJ7s/yHe4tQNLCgAJ

Freeze browser version and unify OS versions (in June 2020).

Unify desktop OS string as a common value for desktop browsers.
Unify mobile OS/device strings as a similarly common value for those at M85 (*) (in September 2020)

Google, privacy nightmare, is imposing their tech for this new stuff. We probably need to deal with this soon.

Event Timeline

revi created this task.Wed, Jan 15, 5:28 AM
revi moved this task from Incoming to Radar on the User-revi board.
Bradv added a subscriber: Bradv.Wed, Jan 15, 5:51 AM
NickK added a subscriber: NickK.Wed, Jan 15, 8:02 AM

As an FYI why this may end up being wasted effort... https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/-2JIRNMWJ7s/yHe4tQNLCgAJ - "Intent to Deprecate and Freeze: The User-Agent string"

I applaud that effort personally. However, the users of this tool rely on that data. They are quite literally trying to fingerprint a user with this information. It's clear from that post that they want to thwart fingerprinting (which, again, I applaud).
We would need to conceive of another way to help the admins using this tool compare edits/users to each other to make the decisions they are trying to make.
Since they are just freezing the feature, it may well continue to serve its purpose in this particular use case.

Since they are just freezing the feature, it may well continue to serve its purpose in this particular use case.

Indeed, it was more making sure people were aware. :) They're talking about alternatives, but nothing is done until it's done
Like everything, it's not gonna happen particularly quickly. So carrying on with some of the implementation probably makes sense, but digging into weird edge cases, and putting much time into enhancing it in various ways might not be worth it

So carrying on with some of the implementation probably makes sense, but digging into weird edge cases, and putting much time into enhancing it in various ways might not be worth it

100% agree. I think our hope was just to roll in an existing FLOSS implementation and let it suffice.

Huji added a subscriber: Huji.Wed, Jan 15, 5:09 PM