| ▲ | hnuser123456 2 hours ago | |
I thought the whole issue with manifest v3 is that prevented extensions from being able to block connections? That DNS blocking is actual blocking, while the extension can only do filtering after the connections are made. | ||
| ▲ | gruez 2 hours ago | parent | next [-] | |
>I thought the whole issue with manifest v3 is that prevented extensions from being able to block connections? No. See: https://developer.chrome.com/docs/extensions/reference/api/d... >The chrome.declarativeNetRequest API is used to block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy. | ||
| ▲ | Daedren 2 hours ago | parent | prev [-] | |
They can block, it just has to be declarative unlike before. It's better than DNS adblockers since you can still do content filtering, CSS/JS injections and whatnot. | ||