-
-
Notifications
You must be signed in to change notification settings - Fork 381
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
Document scoping rules taking action on a domain #1515
Comments
I'm think we should answer these questions for what we'd like to see. Then adapt the code accordingly. I'll dump any answer's I have here. |
|
I tried to answer some of these in comments beginning from #1508 (comment). I think the best way to "document" this sort of code interaction stuff is through unit tests. For example, |
I'm not sure what the actionable items here are. Is it to fill in the missing unit tests? |
I'd like to answer these in writing to help with implementing things like #1508 |
Here is a sample unit test to demonstrate exercising the code we are trying to understand and document: https://github.com/EFForg/privacybadger/compare/sample-blacklistOrigin-tests. Writing this test led me to think that we are discussing an impossible situation: How would a non-yellowlisted base domain get blocked when the yellowlisted subdomain got blocked because of a bad yellowlist update? |
Sorry, I don't think I was being very clear. The issue is about a few related things:
Having 1. written out explicitly would be helpful for implementing 3. I don't think we need to answer all of these questions, and make all of these design decisions at once. I think these will come up individually, like in #1508 If we had something explaining existing rules, and something explaining what future design we'd like to achieve, I think it would have helped guide that discussion. |
A new rule I learned, things in the mdfp list should always be etld+1. See cowlicks@8b2a6ac |
I'm going to resolve this, as I think it makes more sense to document our logic (whether through tests or actual documentation) as part of working on fixing bugs/adding features. |
When deciding what action we should take for a domain, there are many interacting things to consider.
The heuristic action of the basedomain, heuristicaction of the subdomains, is the domain on the PSL, is it a mdfp, is it on the cookieblock list, is it on the disabled sites list, is it third or first party, also user actions, etc.
The way these things interact is not well defined or documented. We need to specify how we want them to interact if we want to be able to fix them.
The text was updated successfully, but these errors were encountered: