Google does not and cannot have any control over any Chromium forks
That is not true. I remember several chromium-based browser developers saying for several changes made by google to chromium that they can’t afford the maintenance burden to reverse it.
One instance of that happening is switching the addon framework to manifest v3, which severely degrades the functionality of browser firewalls, like uBlock Origin, by restricting (for “security reasons”, apparently) the amount of network filters they can apply (and maybe with other changes too, I don’t remember it exactly).
But there were also other instances of this happening, which I don’t remember right now. Maybe also when they released the first version with FLoC.
And then I think these 2 (anti)features (even any of them alone) also qualify for invasions of privacy, and they are present in most of the chromium based browsers.
I remember several chromium-based browser developers saying for several changes made by google to chromium that they can’t afford the maintenance burden to reverse it.
…reverse what?
manifest v3
uBlock already solved this issue and still for other browsers it was never a problem in the first place, because they have domain-blocking built into the browser itself.
That is not true. I remember several chromium-based browser developers saying for several changes made by google to chromium that they can’t afford the maintenance burden to reverse it.
One instance of that happening is switching the addon framework to manifest v3, which severely degrades the functionality of browser firewalls, like uBlock Origin, by restricting (for “security reasons”, apparently) the amount of network filters they can apply (and maybe with other changes too, I don’t remember it exactly).
But there were also other instances of this happening, which I don’t remember right now. Maybe also when they released the first version with FLoC.
And then I think these 2 (anti)features (even any of them alone) also qualify for invasions of privacy, and they are present in most of the chromium based browsers.
…reverse what?
uBlock already solved this issue and still for other browsers it was never a problem in the first place, because they have domain-blocking built into the browser itself.
Know why? Because. They’re. Not. Chrome.
“several changes made by google to chromium”
No, they don’t. They released a lite version that will attempt to do it’s thing in the limited environment of up to date chromium browsers.
(Edit: here are the differences between the normal and this lite version as explained by the developer: https://libreddit.pussthecat.org/r/uBlockOrigin/comments/1067als/eli5_ublock_lite_vs_ublock_origin/j3h00xj/?context=3)
And then here is something new that shows how google can not only easily control chroimum based browsers, but basically every other one too, by creating their own definition of “open web”:
Their vision: https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md
Users thoughts: https://github.com/RupertBenWiser/Web-Environment-Integrity/issues
A specific issue (there are more) where the standpoint of googlers (you are dumb! (does not explain why)) and the users (we don’t want this!) can be clearly seen: https://github.com/RupertBenWiser/Web-Environment-Integrity/issues/36
Discussion on lemmy: https://lemmy.blackeco.com/post/25574