Add OISD-nsfw blocklist #116
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Could OISD NSFW blocklist be added as an option to the blocklists available? There are just soooo many sites missing in the default "porn" list currently used in NextDNS that it's basically useless for any porn/adult content control.
We would really like to purchase NextDNS Business/ Education but with the adult content protection being basically non-existent we will have to go search for a different provider. Just a simple search for the highest traffic adult sites and testing them on your filter shows dozens passing through. The OIDS list is the most extensive and I found it to contain most sites the default NextDNS list isn't catching.