this post was submitted on 19 Jul 2023
1499 points (98.3% liked)

Technology

34989 readers
486 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 3 points 1 year ago (1 children)

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.