You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently upon refresh, we nuke (=completely replace) all whitelists and blacklists from our files. This might not be what the user wants, because he or she might have setup whitelists and/or blacklists of his/her own.
So we need to implement a better way to deal with these lists. Probably some logic like the ADD/MERGE/DELETE/FULL mode for the list_of_blocklists.txt file.
However this is complicated by the fact that for white-/blacklists, stored in the domains table in the Gravity DB, we have no master table like we have for adlists->gravity so there is no possibilty yet to have white-/blacklists grouped together and identify them as a collection of entries.
So probably this needs to be addressed as an enhancement request to upstream Pi-Hole developers.
If so, I will link to relevant communication with upstream here.
The text was updated successfully, but these errors were encountered:
Probably, this could be handled by making use of the Groups feature, although this was meant for a completely different purpose, i.e.for mapping clients to rules/rule sets.
Currently upon refresh, we nuke (=completely replace) all whitelists and blacklists from our files. This might not be what the user wants, because he or she might have setup whitelists and/or blacklists of his/her own.
So we need to implement a better way to deal with these lists. Probably some logic like the ADD/MERGE/DELETE/FULL mode for the
list_of_blocklists.txt
file.However this is complicated by the fact that for white-/blacklists, stored in the
domains
table in the Gravity DB, we have no master table like we have foradlists->gravity
so there is no possibilty yet to have white-/blacklists grouped together and identify them as a collection of entries.So probably this needs to be addressed as an enhancement request to upstream Pi-Hole developers.
If so, I will link to relevant communication with upstream here.
The text was updated successfully, but these errors were encountered: