this post was submitted on 21 Jul 2023
2333 points (99.3% liked)
Privacy
32003 readers
821 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This post title is misleading.
They aren't proposing a way for browsers to DRM page contents and prevent modifications from extensions. This proposal is for an API that allows for details of the browser environment to be shared and cryptographically verified. Think of it like how Android apps have a framework to check that a device is not rooted, except it will also tell you more details like what flavor of OS is being used.
Is it a pointless proposal that will hurt the open web more than it will help? Yes.
Could it be used to enforce DRM? Also, yes. A server could refuse to provide protected content to unverified browsers or browsers running under an environment they don't trust (e.g. Linux).
Does it aim to destroy extensions and adblockers? No.
Straight from the page itself:
Edit: To elaborate on the consequences of the proposal...
Could it be used to prevent ad blocking? Yes. There are two hypothetical ways this could hurt adblock extensions:
Knowing this data and trusting it's not fake, a website could choose to refuse to serve contents to browsers that have extensions or ad blocking software.
Websites could then require that users visit from a browser that doesn't support adblock extensions.
I'm not saying the proposal is harmless and should be implemented. It has consequences that will hurt both users and adblockers, but it shouldn't be sensationalized to "Google wants to add DRM to web pages".
Edit 2: Most of the recent feedback on the GitHub issues seems to be lacking in feedback on the proposal itself, but here's some good ones that bring up excellent concerns:
Browsers developed and distributed by large tech firms have a conflict of interest with holding back or limiting attestation. Attestation enables the web to be restricted in a way that benefits tech firms. For example, Office 365 could require that it is used only on Windows and/or only through Edge.
Similarly to what I brought up, having the ability for websites to trust a (browser, os) tuple could allow for certain browsers to be preferred, simply because they do not support extensions.
How it will create hostile discrimination, and two-tiered services based on whether browsers are attested or not.
The proposal does not do an adequate job explaining how a browser may be attested to.. Would this require something like Secure Boot in order for a browser to be attested to? That would discriminate against users with outdated hardware lacking support for boot integrity, or users who don't have it enabled for some reason or another.
I mean, they said Manifest V3 wasn't supposed to interfere with ad blocking either. Yet here we are. Their power over how people access the web is too great to just trust what they say.
I don't disagree with you. If this gets implemented, the end result is going to be a walled garden web that only accepts "trusted" browsers. That's the concern here for ad blocking: every website demanding a popular browser that just so happens to not support extensions.
My issue is with how the OP framed the post. The title is misleading and suggests that this is a direct attempt to DRM the web, when it's not. I wouldn't have said anything if the post was less sensationalized, laying out the details of the proposal and its long-term consequences in an objective and informative way.
"Google wants to introduce DRM to the web".
With the years of experience that we have with the disasters caused by all of "Google", "wants", "DRM" and "web", how is this not objective and informative enough for a title?
Given Google's history, the assertion made by the title isn't wrong. That doesn't mean that it's objective and informative, however.
The title suggests that the intent is to create DRM for web pages and "make ad blockers near-impossible". From an informational standpoint, it correctly captures the likely consequences that would occur should the proposal be implemented. What it (nor the post body) does not do is provide an explanation, information, or context to explain why the proposal demonstrates the claim that is being made.
The reader is not informed about Google's history of trying to subvert ad blockers, nor are they shown how the proposal will lead to DRMed web pages and adblock prevention. The post is a reaction-inducing title followed by a link to a proposal and angry comments on GitHub. That's not informative; that's ragebait.
Suppose I give the post the benefit of the doubt, and consider the bar for being "informative" to be simply letting people know about something. It's still not objective. I'm not saying the OP should support Google or downplay the severity of the proposal, but they could have got the same point across without including their own prejudices:
"Google engineers propose new web standard that would enable websites to prevent access from browsers running adblockers or website-altering extentions."
For the record: I agree with what this post is trying to say. I just disagree with how it's said. Lemmy isn't hemorrhaging ad money, and it isn't overwhelmingly noisy. We don't need to bring over toxic engagement tactics to generate views.