4 ms·
It still exists, but now “ad blockers” can’t use the blocking API to record and forward metrics on hits. Ad blockers don’t even need the webRequest and webReque
by kuhsaft 2y ago
It still exists, but now “ad blockers” can’t use the blocking API to record and forward metrics on hits. Ad blockers don’t even need the webRequest and webRequestBlocking permissions anymore.
Now, if an ad blocker has webRequest permissions it’s a red flag.
For example https://developer.chrome.com/docs/extensions/develop/concepts/content-filtering#adapt_rules_based_on_observed_requests https://developer.chrome.com/docs/extensions/develop/concept... uses webRequest to send telemetry back to some remote server.
- sunshowers 2y agoThanks, I see how that can help. With Manifest v3, let's say I'm an ad blocker and I want to get access to metrics not to violate privacy, but just to report them to the user (X domains blocked, Y out of Z requests blocked, etc). How would I get access to those metrics?
- kuhsaft 2y agoSeparate permission for debugging only available for development essentially. https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/declarativeNetRequest#testing https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web... Otherwise, you can’t really without more invasive permissions. https://stackoverflow.com/questions/74813523/chrome-extension-declarativenetrequest-get-notified-on-request-blocked https://stackoverflow.com/questions/74813523/chrome-extensio...
- sunshowers 2y agoOh wow, that's wild. Closing the loop on reporting things is such an important part of a trustworthy user experience.