CoreLibs

> This was due to a conflict between AdGuard and Apple iCloud Private Relay. Following your post I arrived at this: https://github.com/AdguardTeam/CoreLibs/issues/1914#issuecom... You might want to let the developer know that posting on the forums is absolutely not “reporting the problem to Apple”. They need to file a proper bug with Feedback Assistant, and ideally spend one of their two yearly Technical Support Incident (TSI) to get priority, seeing as it’s a paid app.

One of the stated goal of MV3 by Google[1] was to avoid extensions with broad permissions: > our new declarativeNetRequest API is designed to be a privacy-preserving method for extensions to block network requests without needing access to sensitive data This MV3-based AdGuard extension still requires a broad permission to "read or modify host data" on all sites[2]: "host_permissions": [ "<all_urls>" ], So what you have now is the same required permission to "read or modify host data" as with MV2, but with a network filtering engine capabilities gated by Google (an advertising company). We can't innovate anymore the filtering capabilities of our content blocker engines as we have been constantly doing over the years. For a recent example, there has been discussions lately with filter list maintainers of whether uBO should s