fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-23 12:52:10 +00:00
Code Issues Projects Releases Wiki Activity

Remove draft status

Browse source
This commit is contained in:
Rohan Kumar 2022-06-04 22:50:08 -07:00
parent 058344c83c
commit b342b803e6
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/posts/layered-content-blocking.md
View file

@ -7,8 +7,6 @@ outputs:
- gemtext
footnote_heading: Notes
---
<p role="note">This post is an incomplete rough draft. Please don't share it yet.</p>
The Chromium team is planning on phasing out Manifest V2, its current set of extension APIs, in favor of Manifest V3. [Manifest V3](https://developer.chrome.com/docs/extensions/mv3/intro/) involves giving extensions less access to page contents. Instead, extensions use new APIs that involve giving the browser simple instructions for page modification. The browser performs those instructions using its own logic; extensions themselves can't access page contents.
This represents a tremendous trade-off: extensions need to be trusted less, but are also less capable. The implications for content blockers (ad-blockers) caused significant backlash.[^1] Mozilla plans on adopting Manifest V3 in Firefox with additional APIs to re-introduce the lost functionality. Discourse on the topic has been polarized, full of oversimplification, and devoid of nuance.