forked from I2P_Developers/i2p.www
added some section headings (per wilde's suggestion)
This commit is contained in:
@@ -1,3 +1,5 @@
|
||||
<h2>What is I2P?</h2>
|
||||
|
||||
<p>I2P is an anonymous network, exposing a simple layer that applications can
|
||||
use to anonymously and securely send messages to each other. The network itself is
|
||||
strictly message based (ala
|
||||
@@ -8,6 +10,8 @@ All communication is end to end encrypted (in total there are four layers of
|
||||
encryption used when sending a message), and even the end points ("destinations")
|
||||
are cryptographic identifiers (essentially a pair of public keys).</p>
|
||||
|
||||
<h2>How does it work?</h2>
|
||||
|
||||
<p>To anonymize the messages sent, each client application has their I2P "router"
|
||||
build a few inbound and outbound "<a href="how_tunnelrouting">tunnels</a>" - a
|
||||
sequence of peers that pass messages in one direction (to and from the client,
|
||||
@@ -27,6 +31,8 @@ to find the other client's inbound tunnels efficiently, but subsequent messages
|
||||
between them usually includes that data so no further network database lookups
|
||||
are required.</p>
|
||||
|
||||
<h2>What you can do with it?</h2>
|
||||
|
||||
<p>Within the I2P network, applications are not restricted in how they can
|
||||
communicate - those that typically use UDP can make use of the base I2P
|
||||
functionality, and those that typically use TCP can use the TCP-like streaming
|
||||
|
Reference in New Issue
Block a user