submitted 1 year ago by dukethorion@lemmy.one to c/privacyguides@lemmy.one

11 comments fedilink hide all child comments

With Google's proposed DRM / Web Environment Integrity project looming, will there be any change to PG's recommended browsers?

I'm sure it's on everyone's radar, but this seems like the absolute antithesis of privacy. There will be nothing private about anything chromium-based if this goes through...

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

[-] ISOmorph@feddit.de 4 points 1 year ago

Is it a privacy issue tho? It's dangerous to the freedom of the internet and an ethical dilemma. But how does it increase tracking potential?

[-] wallmenis@lemmy.one 31 points 1 year ago

It will stop you from using tools like ublock origin which help mitigate tracking.

[-] Karcinogen@discuss.tchncs.de 13 points 1 year ago

The project would only allow "verified" web browsers. This means that the only web browsers you can use are the ones that Google has allowed: owned by big companies. It would prevent smaller, privacy friendly web browsers from being a part of the internet.

[-] dukethorion@lemmy.one 12 points 1 year ago

Not only browsers, but operating system as well. Using GrapheneOS, eOS, or whatever?

Denied. Stock OS only on OUR internet, sorry.

[-] RvTV95XBeo@sh.itjust.works 3 points 1 year ago

The idea of it is as simple as it is dangerous. It would provide websites with an API telling them whether the browser and the platform it is running on that is currently in use is trusted by an authoritative third party (called an attester). The details are nebulous, but the goal seems to be to prevent “fake” interactions with websites of all kinds. While this seems like a noble motivation, and the use cases listed seem very reasonable, the solution proposed is absolutely terrible and has already been equated with DRM for websites, with all that it implies.

It's all a bit nebulous at the moment, but at least initially it seems to me like your browser's "attester" would have a lot of insights into your browsing habits. It also has the potential of killing 3rd party browsers like FF who could lose access to websites unless they jump onboard, and who may still lose access if websites decide not to trust their (hopefully more private) attestation service.

There's still a lot of whatifs floating around because Google just surprise pulled this project out of their ass days ago after working on it in secret for at least a year.

[-] dngray@lemmy.one 2 points 1 year ago

Not unless websites require certain features to be visible, that's the major concern.

this post was submitted on 27 Jul 2023

46 points (100.0% liked)

Privacy Guides

16749 readers

1 users here now

In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.

This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.

You can subscribe to this community from any Kbin or Lemmy instance:

Learn more...

Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!

Want to get involved? The website is open-source on GitHub, and your help would be appreciated!

This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.

Moderation Rules:

We prefer posting about open-source software whenever possible.
This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
No soliciting engagement: Don't ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don't repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.

Additional Resources:

founded 1 year ago

MODERATORS

jonah@lemmy.jonaharagon.net