Chrome are planning to neuter the WebRequest API in their upcoming Manifest V3 changes. They claim this is for privacy and security reasons.

I had a look at the privacy case for these changes, and found that the changes actually do nothing for user privacy, and by breaking several privacy extensions, they will actually worsen the situation:
whotracks.me/blog/manifest_v3_

@sam extensions can log every single network request and even arbitrarily rewrite Content-Security-Policy headers using the API. How is that not a privacy and security issue?

Follow

@da Yes, there is a general privacy issue with extension capabilities, and that is not solved by these changes. The webRequest will still be available for observation.

The Chrome team claim that the Manifest V3 changes to webRequest fix privacy issues. The article I linked shows why this is not the case.

Sign in to participate in the conversation
Mastodon

macbeth.cc is one server in the network