Google previously proposed putting restrictions on the functionality of this API for security reasons, potentially impacting the effectiveness of ad-blockers across all Chromium-based browsers including Chrome and Microsoft Edge.
Think antitrust may have had something to do with their change of heart?
The laughability of preventing content filtering for security reasons should have been so obvious that not even Google could argue that one with a straight face.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
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
Think antitrust may have had something to do with their change of heart?
The laughability of preventing content filtering for security reasons should have been so obvious that not even Google could argue that one with a straight face.
Just because they make a changing chromium doesn’t mean that everyone that has forked chromium needs to take that change.