forked from I2P_Developers/i2p.www
W3C XHTML 1.1 compatibility:
* Replaced UTF-8 mdash with — * Fixed an unterminated img tag. (ugha)
This commit is contained in:
@@ -8,7 +8,7 @@ and freely available.</p>
|
||||
|
||||
<p>Unlike many other anonymizing networks, I2P doesn't try to provide anonymity by hiding the
|
||||
originator of some communication and not the recipient, or the other way around. I2P is designed
|
||||
to allow peers using I2P to communicate with each other anonymously – both sender and recipient
|
||||
to allow peers using I2P to communicate with each other anonymously — both sender and recipient
|
||||
are unidentifiable to each other as well as to third parties. For example, today there are both
|
||||
in-I2P web sites (allowing anonymous publishing / hosting) as well as HTTP proxies to the normal
|
||||
web (allowing anonymous web browsing). Having the ability to run servers within I2P is essential,
|
||||
@@ -70,7 +70,7 @@ used to secure these tunnel routed messages, as described <a href="how_tunnelrou
|
||||
In addition, they can be sent in parallel down multiple tunnels, with the last router discarding
|
||||
duplicates.</p>
|
||||
|
||||
<p><img src="http://dev.i2p.net/~jrandom/wiki/tunnelSending.png" alt="I2P Tunnel sending"></p>
|
||||
<p><img src="http://dev.i2p.net/~jrandom/wiki/tunnelSending.png" alt="I2P Tunnel sending" /></p>
|
||||
|
||||
<p>Some of the messages sent in the network (such as those used to manage tunnels, publish some Leases,
|
||||
and deliver long lived end to end messages) may be instead are sent via
|
||||
|
Reference in New Issue
Block a user