Need to allow for precedence of type over domain

[gorhill]

Currently precedence is:

1. specific type/specific domain
2. specific domain
3. specific type
4. master switch

Which prevent from being able to generally blacklist say, "frames" or "cookies" or whatever for whitelisted domains, unless done expressly through the matrix. I don't like frames or cookies, so I wish I could just blacklist them all the times even for whitelisted sites.

Need more thought on how to provide this without adding complication to the user.

One solution I presently consider is to have a settings which allow a user to auto-blacklists a specific type whenever he/she whitelists a domain. So matrix interaction stays the same, except that paranoid (in a good way) users still have the ability to choose to never trust "frames" or "cookies" or whatever else even for whitelisted domains without further matrix interaction.

[gorhill]

Hmm I think I've got a good way to implement this without some special settings (hidden somewhere on a "user setting" pages). Just a matter of simple logic:

If a type of data is explicitly blacklisted, then for whatever domain which is whitelisted by the user, auto-blacklist these types. Example: I blacklist "cookies", then later whitelist "github.com": "cookies/github.com" will be blacklisted by default. User will have to explicitly remove the blacklist status of "cookies" on "github.com" in order to allow for cookies on github.com. This extra step is acceptable to the user since the user explicitly does not trust "cookies" by default. Thus internally:

user blacklist "cookie"
user whitelist "github.com" ==> "cookie" is auto-blacklisted for "github.com"

then optionally, user whitelists "cookie" for "github.com"

[gorhill]

Duplicate of #29 , but I will close this one because #29 is more specific about the solution.