974
Google's New Web Environment Integrity Proposal Dismissed by Brave, Mozilla, and Vivaldi
(news.itsfoss.com)
this post was submitted on 01 Aug 2023
974 points (100.0% liked)
Technology
37712 readers
179 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Aren't Vivaldi and Brave downstream of chromium though 🤔
Vivaldi and Brave can modify Chromium to disable this feature. Chromium is open source after all.
are they forks? That's what I don't get, who controls the merge controls into Chromium's main branch? It's open source, but who actually says yay or nay on PRs getting in? I assume it's Google, and the others are all forks off, but if it makes it into the main branch or not will really decide if it gets adopted
You can have your own set of patches (and/or config) and still stay up to date with upstream.
You don't need to do a hard fork to modify it for your needs.
They can, but their very existence increases the Chromium engine's market share and therefore Google's control of the web, allowing them to do stuff like this. Once this is implemented in Chrome then these browsers will just become "Chrome but it can't play netflix/access bank websites/etc" or whatever.
Brave calls itself a fork, which I suppose if its truly a fork, they are cherrypicking patches they can use from the chromium base, rather than recompiling with their own patch set on top
Goggle standard approach to it, is to integrate it so much with other components that it will be a lot of work to disable it, eventually making it impractical.
The right way would be for those clients to switch to gecko engine.