The "can not turn off" part is the most jarring. Seriously, did none of Californian PMs hear about the concept of "being multilingual" and not needing to transl

The "can not turn off" part is the most jarring. Seriously, did none of Californian PMs hear about the concept of "being multilingual" and not needing to translate non-English content? --- By the way, this reminds me also of another stupid Google thing related to languages: Say your Chrome is set to English. When encountering another language page, Chrome will (since a decade ago or so) helpfully ask you to auto-translate by default. When you click a button "Never translate <language>", it will add language to the list which is sent out to every HTTP request the browser makes via `Accept-Language` header (it's not obvious this happens unless you're the kind of person who lives in DevTools and inspects outgoing traffic). Fast-forward N years, Chrome privacy team realizes this increases fingerprinting surface, making every user less unique, so they propose this: "Reduce fingerprinting in Accept-Language header information" (https://chromestatus.com/feature/5188040623390720 https://chromestatus.com/feature/5188040623390720) So basically they compensate for one "feature" with another, instead of not doing the first thing in the first place.