Comment on YouTube is deliberately crippling Firefox on ARM systems

• Engywuck@lemm.ee ⁨11⁩ ⁨months⁩ ago

  It looks like also this was against adblocker so, again, not specifically Firefox. Quote from the article itself

  The issue was initially reported as targeting Firefox users, but users online have said they’re seeing the delay in Chrome and Edge, too. Reddit and Hacker News users who’ve examined the code that appears to be causing the delay have said they see no indication that YouTube checks what kind of browser is in use. Mozilla’s senior brand manager Damiano DeMonte wrote in an email to The Verge that “there’s no evidence that this is a Firefox-specific issue.

  source

  • AceSLS@ani.social ⁨11⁩ ⁨months⁩ ago

    Reddit and Hacker News users who’ve examined the code that appears to be causing the delay have said they see no indication that YouTube checks what kind of browser is in use

    That means nothing, this check could be done on the server side and noone would know

    source

    • Engywuck@lemm.ee ⁨11⁩ ⁨months⁩ ago

      I mean… We can we can invent a thousand conspiracies if we want to…

      source
    • kautau@lemmy.world ⁨11⁩ ⁨months⁩ ago

      Except that the delay and browser check is literally in the JavaScript code, you can see it.

      source

      • AceSLS@ani.social ⁨11⁩ ⁨months⁩ ago

        Indeed, but google can just transmit different javascript to different users/browsers/regions etc. It can be decided by a whim and noone would know except some coders at google

        source

        • -> View More Comments
• deweydecibel@lemmy.world ⁨11⁩ ⁨months⁩ ago

  The way I read it is Chrome gets a pass on the architecture crippling, the others don’t.

  Someone correct me if I got the wrong idea.

  source

  • postmateDumbass@lemmy.world ⁨11⁩ ⁨months⁩ ago

    So Google is saying out loud they are trying to be Microsoft and abuse its near monopoy to push their other products.

    Got it.

    source
• theKalash@feddit.ch ⁨11⁩ ⁨months⁩ ago

  Which turned out to also have nothing to do with FF but was targeting adblockers.

  source