Although, I think the biggest issue with I2P is that there's no equivalent to TorBrowser. Some consider it a feature that you can use any browser, as long as you point it at the I2P tunnel, because a lot of people like to use Chrome, but vanilla browsers are vulnerable to all kinds of privacy leaks that TBB protects against. Eepsites can induce vanilla browsers to run Flash and Java, unless you take explicit steps to disable them. There are also issues with state isolation, cross-site identifiers, disk caching, and fingerprinting a la: https://panopticlick.eff.org/ If you run Google Chrome with some unique set of fonts and I run Firefox with another unique set of fonts, we are uniquely identifiable across all eepsites. Here are all the things that TorBrowser protects against, which vanilla browsers don't: https://www.torproject.org/projects/torbrowser/design/ TBB is patched to disable potentially dangerous JavaScript and CSS, without having to disable all JavaScript and break most web sites. So you can either fix all those problems yourself (and apparently some of them can't be fixed in Chrome), or you can use Tor and TBB out of the box. For now, I'll stick with Tor.