this post was submitted on 12 Dec 2023
1194 points (96.6% liked)
Technology
59402 readers
2854 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Oh, they also do that. Just not based on architecture. https://www.theverge.com/2023/11/21/23970721/google-youtube-ad-blocker-five-second-delay-firefox-chrome
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.
So Google is saying out loud they are trying to be Microsoft and abuse its near monopoy to push their other products.
Got it.
It looks like also this was against adblocker so, again, not specifically Firefox. Quote from the article itself:
That means nothing, this check could be done on the server side and noone would know
I mean... We can we can invent a thousand conspiracies if we want to...
Except that the delay and ad blocker check is literally in the JavaScript code, you can see it.
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
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
Which turned out to also have nothing to do with FF but is targeting adblockers.