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
Originally posted by LucioAmely November 16, 2023
The sources and list fetching feature is already implemented in dnscrypt-proxy. Please provide us a convenient way to automatically fetch rulesets and filterlists on all supported platforms.
1.) There will be 2 types of ruleset and filterlist files. One appended with -local and another appended with -remote. Local files will have priority over remote files.
2.) Users will configure remote rulesets and filterlist sources from dnscrypt-proxy.toml together with their own refresh delays.
3.) At app start dnscrypt-proxy will initialize connection to the DNS server using previous rulesets and filterlists if needed. (I do not know if they are being used or needed during the initial connection phase.)
4.) Then dnscrypt-proxy will initiate downloading of rulesets and filterlists configured in the dnscrypt-proxy.toml file and will queue (if queuing not possible then will block) all requests sent to the app until the lists are downloaded and initialized.
The text was updated successfully, but these errors were encountered:
This issue was automatically closed because it did not follow the issue template. We use the issue tracker exclusively for bug reports and feature additions that have been previously discussed. However, this issue appears to be a support request. Please use the discussion forums for support requests.
Discussed in #2530
Originally posted by LucioAmely November 16, 2023
The sources and list fetching feature is already implemented in dnscrypt-proxy. Please provide us a convenient way to automatically fetch rulesets and filterlists on all supported platforms.
1.) There will be 2 types of ruleset and filterlist files. One appended with
-local
and another appended with-remote
. Local files will have priority over remote files.2.) Users will configure remote rulesets and filterlist sources from
dnscrypt-proxy.toml
together with their own refresh delays.3.) At app start dnscrypt-proxy will initialize connection to the DNS server using previous rulesets and filterlists if needed. (I do not know if they are being used or needed during the initial connection phase.)
4.) Then dnscrypt-proxy will initiate downloading of rulesets and filterlists configured in the
dnscrypt-proxy.toml
file and will queue (if queuing not possible then will block) all requests sent to the app until the lists are downloaded and initialized.The text was updated successfully, but these errors were encountered: