Privacy

32121 readers

320 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

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

523

Google is already pushing WEI(DRM Webpage) into Chromium (github.com)

submitted 1 year ago by mastermind@lemm.ee to c/privacy@lemmy.ml

149 comments fedilink hide all child comments

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

[–] 133arc585@lemmy.ml -1 points 1 year ago* (last edited 1 year ago) (1 children)

A fork like Vivaldi, Brave or Opera could opt not to implement these changes

It doesn't quite work like that. They wouldn't choose to not implement the change, because the change comes from upstream via Chromium. They would have to choose to remove the feature which, depending on how it's integrated, could be just as much work as implementing it (or more, if Google wants to be difficult on purpose). Not implementing the change is zero effort; removing the upstream code is a lot of effort.

[–] InFerNo@lemmy.ml 1 points 1 year ago

Perhaps I could rephrase that to "could opt to unimplement". These people are smart enough to check and verify the changes in the browsers that they ship.

These alternative browsers are essentially also forks of chromium. They pull in changes from upstream. I'm not well versed in browser engine development or how these teams keep their engines up to date, but I'm sure there's a person or team responsible for checking and pulling the changes. They could decide to not pull that in, if that code is properly boxed and not all over the place, but still the commits to that feature will show what and where. They still have that choice to stray from upstream, but it might be hard to maintain in the long run if the code is all over the place.