The Trouble with CloudFlare
Tor has acknowledged their &quot;botnet problem&quot; since at least 2013:<p><a href="https:&#x2F;&#x2F;research.torproject.org&#x2F;techreports&#x2F;botnet-tr-2013-11-20.pdf" rel="nofollow">https:&#x2F;&#x2F;research.torproject.org&#x2F;techreports&#x2F;botnet-tr-2013-1...</a><p>That same paper walks through the challenges of dealing with it and doesn&#x27;t find any satisfactory solutions.<p>As I wrote in our post on the topic, there&#x27;s a trade off between security, anonymity, and convenience. CloudFlare provides security to our customers. We believe in the importance of anonymously accessing the Internet. Unfortunately, that means we have to sacrifice some convenience. If you haven&#x27;t read it, I encourage you to see the post I wrote on the topic:<p><a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;the-trouble-with-tor&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;the-trouble-with-tor&#x2F;</a><p>The two long-term solutions we proposed — blinded tokens or CloudFlare supporting .onion addresses — we believe could reduce the inconvenience, but they&#x27;ll require help from the Tor developers. While public posts like this are discouraging in terms of coming up with a better solution, I&#x27;m encouraged by private conversations we&#x27;ve had with Tor developers who acknowledge this is a hard problem and want to find solutions.