467
Hector Martin (@marcan@treehouse.systems)
social.treehouse.systemsAttached: 3 images
Today I learned that YouTube is deliberately crippling Firefox on Asahi Linux. It will give you lowered video resolutions. If you just replace "aarch64" with "x86_64" in the UA, suddenly you get 4K and everything.
They literally have a test for "is ARM", and if so, they consider your system has garbage performance and cripple the available formats/codecs. I checked the code.
Logic: Quality 1080 by default. If your machine has 2 or fewer cores, quality 480. If anything ARM, quality 240. Yes, Google thinks all ARM machines are 5 times worse than Intel machines, even if you have 20 cores or something.
Why does this not affect Chromium? **Because chromium on aarch64 pretends to be x86_64**
`Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36`
🤦♂️🤦♂️🤦♂️🤦♂️🤦♂️
Welp, guess I'm shipping a user agent override for Firefox on Fedora to pretend to be x86.
**EDIT**: The plot thickens. Pretending to be ChromeOS aarch64 *still gets 4K*. Specifically: `Mozilla/5.0 (X11; CrOS aarch64 10452.96.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36` still works.
**EDIT 2**: OK, so the plot *really* thickens now. Chrome is not affected even if it claims to be aarch64. Turns out there is another codepath: apparently YouTube thinks aarch64 Firefox is... a HiSense TV?!?!?!?! Specifically, model 65a67gevs...?????
This is *server-side* sniffing now and it's *specifically* looking for Firefox aarch64 (or at least "Gecko and not Chrome/CrOS/something else known to pretend to be Gecko"). And it's the "TV" platform that is triggering the resolution crippling.
deleted
The thing is, I really don’t think, Google would care about Firefox. Firefox is sitting at negligible percentages of usage share. The only real competitor to Chrome is Safari and that’s because of iOS.
I guess, they might impact Safari on macOS with this, but someone would have to try this out to actually see, and ultimately, this could still just be a dumb mistake.
Having said that, Google holds a near-monopoly in both video content and web browsers. They have a special duty to not disadvantage competitors and even if this was an honest mistake, I do think, it deserves a slap on the wrist.
Google has a history of this sort of “whoops, we got caught, uhhh… That was just a bug!” behavior.
They do have a history of such things happening, yes, which is why my comment exists in the first place. Normally, I would assume this to just be the result of regular shitty management practices paired with regular shitty profit motives.
The history makes it look like they might genuinely have a higher motive here, and I’m saying I still don’t think so, because it would be far too petty and I don’t see them benefitting that much from it.
I want to believe you and I hope you’re right, but I have such little faith in corporations ever doing the right thing anymore.