Black/Whitelist issues

Good day.

1. If I edit the toml file and give a relative path to blacklist_file= then SimpleDNSCrypt will hang while loading, and I will have to kill it, edit the toml file and provide an absolute path.

2. It is unclear to me how the black/whitelists work since the paths that I select for the 3 files are not respected. There a 3 fields: "Blacklist" "Whitelist Rules" and "Blacklist Rules" in that order in the UI. The naming of these fields suggests that the final blacklist should be the first field called "Blacklist" and then we have 2 custom files from SimpleDNSCrypt labelled "Whitelist Rules" and "Blacklist Rules." But this is not how it works, **I think you mis-labelled the fields**. In reality, the "Blacklist" field at the top represents the custom Blacklist Rules for SimpleDNSCrypt, and the final filed labelled "Blacklist Rules" is in fact the final blacklist that will be passed to the proxy.

3. What I want to do ultimately is use a BASE blacklist, which I build with the python script provided in the proxy package, then add custom rules using SimpleDNSCrypt and in the end build a final file that I would pass to the proxy. We are missing a field here: base blacklist [**suggested improvement**]. Basically SimpleDNSCrypt would be an editor for the files that I pass to the python script, i.e. I would never use SimpleDNSCrypt to build the blacklist.

4. However right now **I cannot use SimpleDNSCrypt at ALL** if I want to do this _unless I accept SimpleDNSCrypt's file paths for the black/white and final blacklist_, because as soon as I start SimpleDNSCrypt, and it sees that the blacklist is enabled, it overwrites the path that I put in the toml file and resets it. It does this for quite a few things too - I just cannot use SimpleDNSCrypt since it keeps changing things that I set manually. Manually selected paths to logfiles and blacklists etc should be respected.

Regards,