Editing How to bypass ISP censorship (section)

= Tor vs. I2P Comparison =
''This part of the guide is taken from the [https://geti2p.net/en/comparison/tor i2p projects comparison page].''

{| class="wikitable" style="width:100%; vertical-align:top;"
|-
! Benefits of Tor over I2P !! Benefits of I2P over Tor
|- style="vertical-align:top;"
|
* Much bigger user base; highly visible academic and hacker community support.
* Solved scaling issues I2P hasn't addressed.
* Significant funding and funded developers.
* More resistant to state-level blocking due to TLS transport layer and bridges.
* Designed and optimized for exit traffic (large number of exit nodes).
* Better documentation, formal papers, and translations.
* More efficient memory usage.
* Low bandwidth overhead for client nodes.
* Centralized control efficiently addresses Sybil attacks.
* High capacity core nodes provide higher throughput and lower latency.
* Written in C.
|
* Designed and optimized for hidden services, which are much faster than in Tor.
* Fully distributed and self-organizing.
* Peers selected by continuous profiling rather than trusted claims.
* Floodfill peers ("directory servers") are untrusted and vary.
* Small enough that it hasn't been blocked or DOSed much.
* Peer-to-peer friendly.
* Packet switched instead of circuit switched (transparent load balancing, resilience via parallel tunnels).
* Unidirectional tunnels instead of bidirectional circuits (doubles nodes an attacker must compromise).
* Short-lived tunnels decrease active attack vectors compared to Tor circuits.
* Essentially all peers participate in routing.
* Written in Java.
|}