Dear @jedisct1,
Previously, the announcement of the new version of DNSCrypt caused joy and interest in finding out as soon as possible how the lives of privacy-concerned people would change for the better. But now it's just scary to look at the news, because there are more and more unexpected features that hardly fit into the existing workflow..
Specifically, v2.1.9 introduced a hot-reloading of config files. As a result, memory consumption increased from 26 MB top to 36 MB and growing. CPU has become more noticeable: it wakes up much more often from a lower power consumption mode, which is accompanied by an unpleasant sound. And I'm worried that some app may change those config files.
I tried to find a flag or an option in the toml settings to turn this feature off, but no luck there. What can be done? Roll back to 2.1.8?
Dear @jedisct1,
Previously, the announcement of the new version of DNSCrypt caused joy and interest in finding out as soon as possible how the lives of privacy-concerned people would change for the better. But now it's just scary to look at the news, because there are more and more unexpected features that hardly fit into the existing workflow..
Specifically, v2.1.9 introduced a hot-reloading of config files. As a result, memory consumption increased from 26 MB top to 36 MB and growing. CPU has become more noticeable: it wakes up much more often from a lower power consumption mode, which is accompanied by an unpleasant sound. And I'm worried that some app may change those config files.
I tried to find a flag or an option in the toml settings to turn this feature off, but no luck there. What can be done? Roll back to 2.1.8?