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.
  • fosforus@sopuli.xyzEnglish
    328·
    2 years ago

    Steelmanning: perhaps no ARM Linux system was capable of playing 4K reliably until Asahi Linux came along?

    • Flaky@iusearchlinux.fyiEnglish
      42·
      2 years ago

      Someone on the Hacker News cross-post mentioned it, but it seems like they assumed any ARM Linux device that wasn’t detected as running Android was some low-power device like a Raspberry Pi, and didn’t anticipate more powerful devices running bog-standard Linux until Apple Silicon and thus Asahi came along.

    • whfsdude@dmv.socialOPEnglish
      243·
      2 years ago

      It’s probably the case that this was good intent given the lack of desktop ARM computing hardware, but they really should let the client decide the video quality.