If you build censorship-resistant tools, first, thank you, and second, maybe you'll be interested in some actual censorship first-hand experience. In Russia, they've gone mad in fighting against VPNs. On my home connection, basically half of the internet is restricted to something like 16KB upload or download, then the connection is terminated. Popular facilities like cloudflare or AWS suffer first, against any logic of collateral damage. Obscure LN hostings usually fare better. Today I've published my first repo (tclnostr) with ngit, using my VPN, after several unsuccessful attempts to do it directly via my home network. I expected ngit to take HTTPS_PROXY from my env (which points to the tunnel to normal internet), but it did not happen. If you build censorship-resistant tools, consider supporting proxies from environment, or some other way to specify an outbound SOCKS5 or CONNECT proxy. For me, there is not always a default route that works, but there is always some tunnel. Consider openssh: it ignores the environment, which is a minor inconvenience, but with its ProxyCommand I can connect via any tunnel, thanks to socat (and netcat).