Reply to thread

Message

<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1036957">When you have a lot of users and a lot of data entries and many data sets (blocklists), creating a blocklist per user is not an efficient approach. An alternative is to create a master (superset) with partition pointers for each blocklist that user has enabled. The data needed per user is simply a vector array containing pointers to the blocklist (partition) optimised for DNS filtering. Because this is all performance critical stuff it probably is not implemented using relational data bases, but low level displacement pointers. When you disturb the chain of pointers, everything needs to be tested thoroughfully which is a lot of work for something that is only an optimization of disk space.Even when NextDNS did not want to change the mechanism of personal DNS blocklists, they could have simply removed them from the NextDNS my.nextdns.io management console (not removing in the blocklists from the block mechanism itself, but simply removing them as an option to choose). This simple UI-cleanup would not cost a lot of development manpower. I agree it looks silly to offer blocklists which have not been updated for two years.</blockquote>

[QUOTE="ForgottenSeer 97327, post: 1036957"] When you have a lot of users and a lot of data entries and many data sets (blocklists), creating a blocklist per user is not an efficient approach. An alternative is to create a master (superset) with partition pointers for each blocklist that user has enabled. The data needed per user is simply a vector array containing pointers to the blocklist (partition) optimised for DNS filtering. Because this is all performance critical stuff it probably is not implemented using relational data bases, but low level displacement pointers. When you disturb the chain of pointers, everything needs to be tested thoroughfully which is a lot of work for something that is only an optimization of disk space.Even when NextDNS did not want to change the mechanism of personal DNS blocklists, they could have simply removed them from the NextDNS my.nextdns.io management console (not removing in the blocklists from the block mechanism itself, but simply removing them as an option to choose). This simple UI-cleanup would not cost a lot of development manpower. I agree it looks silly to offer blocklists which have not been updated for two years. [/QUOTE]

Verification