logoalt Hacker News

eikenberry • 10/11/2024 • 2 replies • view on HN

If I remember right then the difference is more about ad-tracking/privacy than blocking. V2 allowed UBO to find and intercept the calls to the ad servers before the calls were made. Where V3+UBL still makes the calls it just doesn't display the results. So while you might not see the ads, the ads see you.

Replies

crazygringo • 10/11/2024

> Where V3+UBL still makes the calls it just doesn't display the results. So while you might not see the ads, the ads see you.

That's not what the docs say [1]:

  A single rule does one of the following:

  - Block a network request.
  - Upgrade the schema (http to https).
  - Prevent a request from getting blocked by negating any matching blocked rules.
  - Redirect a network request.
  - Modify request or response headers.
Does "block" not mean block? Can you provide a source? Or am I looking at the wrong docs? I'm searching online and can't find anything that says the request is still sent.

[1] https://developer.chrome.com/docs/extensions/reference/api/d...

kuhsaft • 10/11/2024

On the contrary, MV2 used onBeforeRequest which let extensions see what requests you were making. They could then take that data and use it for malicious purposes.

MV3 doesn’t allow extensions to know what requests are being made, so extensions can’t use your data maliciously.

Requests to ads that are blocked are blocked.

I think you’re thinking of Privacy-preserving ad measurement which is an option in Firefox and Safari. https://support.mozilla.org/en-US/kb/privacy-preserving-attr...

➕ show 3 replies