nextdns
Clefspeare13/pornhosts
Do to the take down by Github, the earlier announced time for merging the sourced records from the clefspeare13/pornhosts into Pron-Records have arrived and have happened when you read this README. It means all records now are 100% controlled by Pron-Records without exceptions.
This means all future builds are done from the earlier submit_here folder + the matrix of files used to build a hosts, Pi-hole and AdGuard blacklist
Source: https://mypdns.org/clefspeare13/pornhosts/-/tree/master/#pornhosts-a-consolidated-anti-porn-hosts-file
Even the hosts list is continued as usual, and will be that for a long period of time, then my personal recommendation would be that there would be a way to include several plain lists as that would keep this filter way more up to date, as you could benefit from importing directly from Porn-Records
Thanks for the reminder by @Rexadev in https://github.com/tiuxo/hosts/pull/29#issuecomment-992761482
The PR-project now also contain the work from @ShadowWhisprer which means there are ~90.000 new records. And as always, everything will only be import by manual verification.
NextDNS has stopped using Clefspeare13/pornhosts after this https://github.com/nextdns/metadata/issues/834#issuecomment-992782275 post because non of the sites add to mypdns/porn-records are blocked by NextDNS
@rs, @emilstahl Would it be possible to at least have a reply for this PR, 3 weeks an not even a comment from those with merge right is a long time.
Last I heard NextDNS was going to be doing all porn filtering in-house and these 3rd party lists I expect would eventually be dropped. That's probably why they are not merging?
