1st-party tracker blocking with Chrome

[mikhoul]

Hi @jspenguin2017 ,

Are you going to find a solution for the 1st-party tracker in Chrome with Nano ?

uBlockOrigin/uBlock-issues#780

Regards

[liamengland1]

When it comes to uBo stable it will come to Nano, most likely.

[jspenguin2017]

I'm not very familiar with the implementation details of the feature upstream, but from what I've seen so far, I don't really like how it's implemented. I think existing filters are not written to expect resolved (or uncloaked) CNAMEs, and a user-maintained cnameAliasList in the advanced settings page is not going to scale very well.

As for that specific issue, it can probably be fixed with whitelisted-only rules (block all subdomains except specific ones). It needs to be handled on a case by case basis but I think there might be ways to automate it. I think that would be a cleaner and safer solution than universally resolve CNAMEs.

[jspenguin2017]

@llacb47
The code will be pulled/synchronized over, but the feature isn't going to work on Chromium due to missing/different extension APIs.

[jspenguin2017]

@xlollomanx
Be sure to cite your sources, "read somewhere" is not convincing enough to form an argument. Also, don't go off topic, the discussion issue about Manifest V3 is here.