In many counties, users have their OS/Browser settings set to English only, when they actually also speak other languages (or in certain countries, exclusively other languages). There's also a bunch of complexity in regards to spoken/written language comprehension, but I won't get into that here.
There is much more engagement when Google presents content in languages people actually know (or, rather, languages Google thinks they know), regardless of what their Accept-Language header is.
Unfortunately, I cannot present you with hard stats, as I no longer work there. I'm sorry that's unsatisfactory, and I'm not asking you to blindly trust the word of a stranger. Just wanted to offer up some insight into why the system behaves as it does sometimes.
Unfortunately, thats just not true. Accept-Lanuage is set to English most of the time, even for people in non-enlish speaking counties. It's not that they cannot use English, it's that experiments show that users are more likely to interact with content that is in their predicted language, even when Accept-Language is set to English.
Except, in non English speaking counties, the vast majority of people do not change the Accept-Language header (through various browser/OS mechanisms), and receive default results. But then experiments show that they are more likely to interact with pages when shown in the languages Google thinks you actually use.
If you go to myaccount.google.com/language , you can remove languages you don't actually speak, or turn off automatically adding languages altogether. It doesn't always work for everything, but it's a good signal.
I agree there should be a way to force this better, but there's a bunch of work being done on it.
You can add a hl=en parameter to the URL, and most Google apps will respect it.
Except I've been able to do medium complexity tasks in various Autodesk products(Inventor, 3ds Max) within minutes of opening the program for the first time, without looking at any documentation. While I struggle to do even simple tasks in blender, even with many hours of going through tutorials. I try to pick it up again every few years, and inevitably give up several weeks in.
Are you trying to claim that locking your door at night, and carrying a firearm daily, both result in the same amount of risk of life threatening downsides? Because I would very much disagree with that statement.
Locking your door at night is extremely unlikely to have any life threatening downsides. I suppose you could concoct a scenario where you live with someone with an altered mental status and the locked door prevents them from escaping during a fire, but that's reaching.
I use a Nuc clone to run Home Assistant, and AI event detection for my camera network (assisted by a Coral accelerator). So I think it legitimately qualifies for those buzzwords.
> Teslas do phone home a lot for other stuff, but for better or worse, so do most other modern-day cars. And the Tesla UI is pretty zealous about asking for your permission for all the things.
How many other cars send your private videos to HQ to be shared among employees on internal meme pages?