Technology

58108 readers

4981 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

1061

YouTube is deliberately crippling Firefox on ARM systems (social.treehouse.systems)

submitted 9 months ago by whfsdude@dmv.social to c/technology@lemmy.world

156 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] AceSLS@ani.social -2 points 9 months ago (2 children)

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

[–] Engywuck@lemm.ee 8 points 9 months ago

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

[–] kautau@lemmy.world 1 points 9 months ago* (last edited 9 months ago) (1 children)

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

[–] AceSLS@ani.social 0 points 9 months ago* (last edited 9 months ago) (1 children)

Indeed, but google can just transmit different javascript to different users/browsers/regions etc (that's why browsers have useragents, so websites can improve browser compatibility according to the circumstances). It can be decided on a whim and noone would know except some coders at google

[–] kautau@lemmy.world 1 points 9 months ago* (last edited 9 months ago)

Except everyone would know. Multiple people across the globe testing different browsers have looked at the same JavaScript code that is being sent to the browser. The check is there, client-side, google isn’t sending a different JavaScript payload for different browsers. Like you said, they could, but that’s not how it currently functions