Hector Martin (@marcan@treehouse.systems)
social.treehouse.systems
Attached: 2 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.
  • blind3rdeye@lemm.eeEnglish
    1·
    11 months ago

    Google has teams of highly paid expert engineers who’s entire job is to maintain and develop youTube. What do you think is more likely:

    1. Google’s engineers were unable to tell that performance in Firefox is degraded by their changes.
    2. Google sees it as advantageous to disadvantage their competitors - including Firefox. And although they might not be able to do it deliberately, for legal reasons, they can still do it by introducing platform specific changes and strategically neglecting to make it work properly.
    • Gestrid@lemmy.caEnglish
      2·
      11 months ago

      I mean, Google’s engineers also recently lost six months worth of a lot of people’s Google Drive files, so, honestly, anything’s possible.

    • Aux@lemmy.worldEnglish
      12·
      11 months ago

      Have you actually checked the code? It doesn’t target Firefox at all. Man…