Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
This repository has been archived by the owner. It is now read-only.
When enabling 'auto whitelist' cannot disable per-site #221
Comments
|
Problem is that a "graylist" state is represented internally by the absence of rules, the default state of all cell. Thus un-whitelisting is essentially the removal of a rule, which put back the cell in its default state -- this is also why there is no visual at all for the persisted state of a graylisted cell. In short, at this point I don't know how I would solve this issue. Need to think more. Edit: Was there a scope in this particular case? If there is a scope, I can envision a solution where an internal switch per-scope would allow to disable auto-whitelist just for that particular scope. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So if you enable the 'auto whitelist first party domain' rule you can't go to a website, unwhitelist the domain, lock it, and then have it persist. If you reload that domain will be whitelisted again.
I think the expected behavior of the user is that the domain would be whitelisted upon first visit, but not be some permanent setting.
The text was updated successfully, but these errors were encountered: