Closed d3ward closed 1 year ago
I added that rule because you check domains, which are not used for ads(as sources) and for tracking.
googleadservices.com
- just a clicktrough links (for example, context ads in google search, which blocked by element hiding rules)ads.google.com
- not used for adsamazon
domains - for ads used c.amazon-adsystem.com
Where are used another domains from the test?analytics.facebook.com
- also is not used for tracking, and now it redirects to https://www.facebook.com/business/help/966883707418907advertising.twitter.com
- same as FBadsdk.yandex.ru
, extmaps-api.yandex.net
not used for ads.
an.yandex.ru
- used for adsmc.yandex.ru
, mc.yandex.com
- analyticsBy this test you are forcing the filter developers to block domains that should not be blocked.
Also used colors - it the pain for eyes, too contrast.
I added that rule because you check domains, which are not used for ads(as sources) and for tracking.
This, at least to me, doesn't make too much sense. I don't see the reason to adopt this aggressive rule because of the list of hosts that are redirects/clicktrough. If they are harmless, why block them by blocking everything else? Although I agree that these hosts are not ads/trackers, so running a test on them is pointless.
By this test you are forcing the filter developers to block domains that should not be blocked.
Didn't know I had that power. I still don't understand how I can force developers to block a domain for a simple test. Maybe you mean that users started complaining that Adguard wasn't working or something, but it's somehow not my fault, I explicitly say that the test is just a test and there may be problems. The project is open, I do my best to improve it, and I listen to user feedback.
Also used colors - it the pain for eyes, too contrast.
Yes, I'm aware of that and have received a lot of feedback about it. The project design is years old and I'm working on an update.
Thanks for the quick and honest reply. I think what we can do there, so that both can benefit, is
This, at least to me, doesn't make too much sense.
That rule was added to the filter, disabled by default. But I can remove it. I hope you will change tested domains list to real(used for hosting ads).
Didn't know I had that power.
But your tool have:) Many users complain that the test scores are low, and some rules were added to EasyList to block domains from the test.
@Alex-302 Thank you ! Meanwhile I have removed the domains that were discussed. Will also keep them removed on the next update of the project.
Thanks!
Prerequisites
What product do you use?
Other ad blocker
AdGuard version
2.1.46.59
What type of problem have you encountered?
Website or app doesn't work properly
Which browser(s) do you use?
Chrome
Which device do you use?
Desktop
Where is the problem encountered?
https://d3ward.github.io/
What filters do you have enabled?
AdGuard Annoyances filter
What Stealth Mode options do you have enabled?
No response
Add your comment and screenshots
I've recently received hundreds of reports from users saying that some of my projects (public and private) no longer work as expected. I found out that Adguard updated the annoyances list with a very strange approach related to one of my projects, the adblock test. Here is the commit of the change: https://github.com/AdguardTeam/AdguardFilters/commit/137b1d9410091d0a675b077d02505ab20a7c0b06
Basically my very simple adblock test https://d3ward.github.io/toolz/adblock.html does a check on the most popular hosts of a couple of categories, this projects works and has helped a lot of users, it works as expected with different DNS solutions, adblock extensions and more. Unfortunately not with Adguard products, though the lists works In the past I had a discussion with someone from Adguard team and we agreed that Adguard solutions are different, and somehow the adblock test have false positive because of how Adguard products works, which does not mean that Adguard does not work! When I use the Adguard lists annoyances with solutions like uBlock Origin, the test adblock works as expected and is not "useless test".
$third-party,domain=d3ward.github.io,important
it's kind of too much, it's block every external api call that start from the domain "d3ward.github.io" , in practice, my main domain is now considered even more annoying than any other ad provider, tracker or otherwise. The rule it's blocking even a simple Github API call I use on my portfolio ->I would like to see this resolved and perhaps open a discussion on what solution we can work on. I'm happy to provide any information, how the adblock test works, which rule should be used instead, etc. I'm aware that users are using the adblock test and thinking that Adguard is not working, and this is causing some confusion. I'm actually working on updating the test to be more clear and specific for only a set of adblocker solutions
Privacy