this post was submitted on 25 Jul 2023
1086 points (98.7% liked)

Firefox

17884 readers
16 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 74 points 1 year ago (5 children)

Sure thing. With this current proposal, when you visit a website, the site asks your browser if you're willing to display it as intended, basically with all and any adverts. If the answer is no, then you can't see the content, if the answer is yes, then you're likely using Chrome or a Chromium based browser and Google can guarantee more ad impressions, because they're first and foremost an advert selling company.

[–] [email protected] 24 points 1 year ago (2 children)

I may not be 100% right, as I haven't looked at it in detail, but I think it's even a bit more than that. Since the way that's proven is by the browser vendor signing the request (I assume with an HTTP header or something), you could also verify it's from a specific vendor. So even if Mozilla says, yes, we'll display your ads, a website could still lock down to Chrome. It would probably also significantly hamper new browsers, and browsers with a security/anti-ad focus, as they won't be recognised by major websites that use the new protocol until they have market share, which they won't get if they don't have access to major websites.

[–] [email protected] 4 points 1 year ago (1 children)

I mean, they already do that by filtering out user agents. But this is certainly a step beyond.

[–] [email protected] 5 points 1 year ago

Which is why all browsers cross identify as other browsers. This would make it easier for sites to block and harder for browsers to work around.

[–] [email protected] 4 points 1 year ago (1 children)

Why can't your browser lie and say "yes of course I'm displaying everything my fingers definitely aren't crossed behind my back"?

[–] [email protected] 4 points 1 year ago

Because it's not just going to say yes. It's going to say yes, and then present an unique key that browser made for themselves. Other browsers might be able to spoof the key, but the proposal might have cryptographically expensive to even try.

[–] [email protected] 3 points 1 year ago

Thanks so much, I understand now. God, is that a shitty move for Google to pull

[–] [email protected] 1 points 1 year ago (1 children)

What about replying yes, then blocking ads?

[–] [email protected] 1 points 1 year ago

Your device would return a signature to say that there's no adblocking software on the device.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (4 children)

That’s not true - you can still use ad blockers etc as normal.

It’s also not a browser check, it’s a device check. It’s to check that the device can be trusted, like android itself hasn’t been tampered with.

[–] [email protected] 15 points 1 year ago* (last edited 1 year ago) (1 children)

That's equally stupid though... why shouldn't I be able to tamper with my phone's operating system? And how is it any of a website's business if I do?

[–] [email protected] 13 points 1 year ago

It's literallly impossible for there to be a valid reason for a website to be entitled to know that under any circumstances.

[–] [email protected] 5 points 1 year ago (1 children)

So people with custom roms or on various Linux distros would be fucked?

[–] [email protected] -2 points 1 year ago (1 children)

Well with custom roms they already are for many apps.

[–] [email protected] 1 points 1 year ago

True, but that's within their own ecosystem. The internet is not owned by Google. But I guess a certain part of the majority wants it that way with how popular Chromium based browsers are.

[–] [email protected] -1 points 1 year ago

How could it not be a browser check if the website relies on the browser to be a middle man? The WebDRM that was pushed by a terrorist organization W3C, currently requires per-browser licensing.

Per wikipedia:

EME has been highly controversial because it places a necessarily proprietary, closed decryption component which requires per-browser licensing fees into what might otherwise be an entirely open and free software ecosystem.