>>14800
Thanks. Yeah, I agree. When I next do big work on the network engine, I will be making some UI for the 'domain manager', and more per-domain tools, so the system will be better able to detect 'ah, this site is down' and not affect the whole system. When I have that up, I could migrate the proxy options to that new system and UI and change depending on domain.
The new 'no_proxy' setting, btw, seems to be ignored due to a bug with the networking library I use (
requests), so with luck that should be fixed soon, which may make things easier in the meantime. If there is any way you can set up a system-wide TOR proxy, that hydrus can inherit with no proxy settings or a careful 'no_proxy', it might be possible to figure out multiple proxies for certain sites more quickly than waiting for me to develop it. This might only be reasonable to do on Linux, though, where there is better support for mapping this sort of thing.