Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove AdGuard CNAME-Cloaked Trackers #21

Closed
Yuki2718 opened this issue Dec 20, 2022 · 12 comments
Closed

Remove AdGuard CNAME-Cloaked Trackers #21

Yuki2718 opened this issue Dec 20, 2022 · 12 comments
Labels

Comments

@Yuki2718
Copy link

Yuki2718 commented Dec 20, 2022

They're periodically imported to EP with problematic domain removed, so it's no need, and even worse does casue trouble. I could reproduce part of trouble in AdguardTeam/cname-trackers#8 (comment) if the list is enabled on uBOL. This is their stance about the list: AdguardTeam/cname-trackers#8 (comment).

gorhill added a commit to gorhill/uBlock that referenced this issue Dec 20, 2022
@SampeiNihira
Copy link

SampeiNihira commented Dec 20, 2022

The "AdGuard CNAME disguised trackers list" (it would probably be better to rename this list) contains more CNAME rules than "EP" and also than "AdGuard Tracking Protection filter."
Even if it breaks a few websites the protection from CNAME trackers is greater.

P.S.

But I understand that in the absence of inserting exception rules it can become a big problem.

@SampeiNihira
Copy link

  • Would it be problematic for a user who does not want broken websites to deselect the list?

  • Or select the "no filtering" option for the specific broken website?

Personally I don't care that much,but if asked I would consider removing the list unnecessary.

@Yuki2718
Copy link
Author

it would probably be better to rename this list

Yes, as "ANY cname of some tracking vendor's domain list regardless if tracker or not". It has some additional click-through tracker which few user would ever come across while the rest does not enhance privacy, more of a false sense of privacy.

@MasterKia
Copy link
Member

gorhill/uBlock@73c50a4

It should be removed from the extension description on the Chrome store as well.
https://chrome.google.com/webstore/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh

@gorhill
Copy link
Member

gorhill commented Dec 26, 2022

gorhill/uBlock@65a3cdd

@gorhill
Copy link
Member

gorhill commented Jan 4, 2023

The list is gone in 0.1.22.12266.

@gorhill gorhill closed this as completed Jan 4, 2023
@gorhill gorhill added the fixed label Jan 4, 2023
@SampeiNihira
Copy link

AdguardTeam/cname-trackers#75

I ask if it is possible to reconsider this choice considering the news listed by Shavaleleka.

@Yuki2718
Copy link
Author

Yuki2718 commented Jun 15, 2023

Any decision will be made by actual benefit to all user based on real-world usage than to some geeks' satisfaction. The major reason of

contains more CNAME rules

is exactly AdguardTeam/cname-trackers#51 , there's little difference in actual tracking protection in which some user would never get any benefit (the biggest factor other than browsing habit here is region). Besides, removing microsites/landing pages/clickthrough domains does not completely solve the afformentioned or known problems as some breakage don't fall into any of the catogory, though I admit they're the most common problems.

Reminder: there is an upper-limit in the number of availabel lists in MV3.

@SampeiNihira
Copy link

SampeiNihira commented Jun 16, 2023

The CNAME combined_disguised_ads.txt filter list has only 23202 total rules:

https://github.com/AdguardTeam/cname-trackers

P.S.
I did a test by entering only EasyPrivacy and the CNAME ads list in UBO.
The CNAME list maintains all the rules.
And only 7 rules from the EasyPrivacy list evidently are surplus:
2

@Yuki2718
Copy link
Author

Yuki2718 commented Jun 16, 2023

@SampeiNihira If you're not aware, disguised_ads is not included in EP, EL, or AGTPF. It's included only in AG Base. This does not mean uBO with standard settings is not protected against them - we have many generic and regex rules to catch them; however, none of these is perfect and even disguised_ads list occasionally fails as these cname adservers are rapid changer (can't find an example issue, GH search is tr**h). Perfect protection comes only by DNS (uBO on Firefox, AG apps with DNS filtering, or other DNS solution). But a question is who needs that - unlike cname tracker which is impossible not to encounter, cname adservers are almost exclusively used on pirate sites, dubious streaming & porn sites, and some link shortner.

@SampeiNihira
Copy link

I understand your point of view Yuki.
And excuse me for these interventions of mine that may annoy.
I only wish to bring to your attention a more general point of view that is shareable with a wide audience of your possible users.

Conclusion.
My only example is due to the fact that with UBO Lite you cannot select the basic AG filter list.
With this intervention,I conclude.
You of course act as you see fit.
Good evening to you all

@Yuki2718
Copy link
Author

Yuki2718 commented Jun 16, 2023

Well, I guessed misunderstanding so added explanation, that's all - if I ever feel annoying, I'm free to say so or ignore. Sorry if my comments sounded authoritative. The only thing I wanna correct is your possible users - uBO is from the beginning "By user, for user" - it's not someone's property. All of us, even gorhill, are just user and the project is maintained by those user spending some time for all user. I hope uBOL does not suffer the same fate as uMatrix for which too many people only demanded features without contributing back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants