AdGuard hard-wires rules specifically for this test domain, and it would be best to take the valid subset of the feedback into account

[thestinger]

https://github.com/AdguardTeam/AdguardFilters/blob/ad7ba2570a953157c09eb8aed0d1fbac7cf03d44/SpywareFilter/sections/specific.txt#L4168-L4200

As an example, this complaint of theirs could be fixed:

! Google Analytics admin panel. We're blocking what's required on this web site, but more granuralry (i.e. `/collect` location). Unfortunately, this test check for the whole domain blocking, hence here's a rule
||analytics.google.com^$domain=d3ward.github.io

This is simply cheating at the test because they don't want to block something breaking sites:

! Blocking of this domain may break Yahoo apps
||log.fc.yahoo.com^$domain=d3ward.github.io

My suggestion is to go through AdGuard's list, fix all of the valid issues they've complained about and then create an organization to move this repository to where it can work properly again once the valid issues are fixed. For domains/URLs that are actually used for ads/tracking which are not being blocked to avoid breaking sites, that seems perfectly fine. The ad blocker is simply making a trade-off and not showing as 100% is fine.

The current status quo is that the test essentially doesn't work, and it makes ad blockers which are not hard-wiring blocking for the test look worse than they should compared to ones that are.