@Winter > My IP address was consistently blocked as a Tor node. It's probably more correct to say it was blocked for consistently malicious activity. I've seen plenty of exit nodes get dropped into my firewall for their behavior, but the only reason I knew they were Tor is because the subnet was specifically labeled as being Tor. @Jasmine > A common recommendation is to run it from a separate IP. It’s easy if you’re running an IPv6-only exit, whereas not all ISPs give multiple IPv4 addresses. This is poor advice. IP addresses don't exist in isolation, and anybody with a thoughtful approach to security is going to blacklist hostile *networks* rather than playing wack-a-mole with individual hosts. Nobody should be under the illusion that using multiple addresses (v4 *or* v6) from the same ISP is going to safeguard your non-Tor traffic. You are known by the company you keep, and Tor makes it easier to be in the neighborhood of hostile traffic. > I don’t know another good way to access schneier.com, for example, without Bruce(‘s provider) or my ISP seeing. A number of protocols *could* be used, but you'd really have to get Bruce to buy into one to make it work well. I'm reminded of things like Usenet, where messages got shared/broadcast throughout the network by default. Sadly, the web has moved us away from those kinds of distributed systems. There are plenty of peer-to-peer networks that could be leveraged to work similarly, or layers put on top of HTTP that allowed content to be served by any number of anonymous/independent proxies. Until the needs of content providers are taken into account, though, things like Tor are non-starters due to their use by bad actors. 51f1bf4ef1d49e584429f86832f5a5d679d23a4bab89510a1e3f3925e35a5d5f