I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Finished migrating docs/how/intro

Browse Source
This commit is contained in:
str4d
2012-09-17 01:04:51 +00:00
parent 5c47ddde0b
commit 62a7de51e7
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
i2p2www/pages/site/docs/how/intro.html
View File

@ -25,7 +25,7 @@ or even taken over to attempt more malicious attacks.</p>
where messages are addressed to cryptographic keys (Destinations) and can be significantly larger
than IP packets. Some example uses of the network include "eepsites" (webservers hosting normal web
applications within I2P), a BitTorrent client ("I2PSnark"),
or a distributed data store. With the help of the <a href="i2ptunnel">I2PTunnel</a> application,
or a distributed data store. With the help of the <a href="{{ site_url('docs/applications/i2ptunnel') }}">I2PTunnel</a> application,
we are able to stream traditional TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and
even streaming audio. Most people will not use I2P directly, or even need to know they're using it.
Instead their view will be of one of the I2P enabled applications, or perhaps as a little controller
@ -63,7 +63,7 @@ the Kademlia algorithm) for distributing routing and contact information securel
<p>In the above, Alice, Bob, Charlie, and Dave are all running routers with a single Destination on their
local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1,2,3,4,5 and 6),
local router. They each have a pair of 2-hop inbound tunnels per destination (labeled 1, 2, 3, 4, 5 and 6),
and a small subset of each of those router's outbound tunnel pool is shown with 2-hop outbound tunnels.
For simplicity, Charlie's inbound tunnels and Dave's outbound tunnels are not shown, nor are the rest of
each router's outbound tunnel pool (typically stocked with a few tunnels at a time). When Alice and Bob
@ -122,10 +122,10 @@ The size of the network (N) bears no impact.</p>
<a href="http://java.sun.com/products/jms/index.jsp">JMS</a>, then grew into its own as an
'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest starting in August '03.
I2P is currently under development, following
the <a href="roadmap">roadmap</a>.</p>
the <a href="{{ site_url('volunteer/roadmap') }}">roadmap</a>.</p>
<h2>Who?</h2>
<p>We have a small <a href="team">team</a> spread around several continents, working to advance different
<p>We have a small <a href="{{ site_url('team') }}">team</a> spread around several continents, working to advance different
aspects of the project. We are very open to other developers who want to get involved and anyone else
who would like to contribute in other ways, such as critiques, peer review, testing, writing I2P enabled
applications, or documentation. The entire system is open source - the router and most of the SDK are
@ -140,7 +140,7 @@ join us on the IRC channel #i2p (hosted concurrently on irc.freenode.net, irc.po
There are currently no scheduled development meetings, however
<a href="{{ url_for('meetings_index', lang=g.lang) }}">archives are available</a>.</p>
<p>The current source is available in <a href="monotone.html">monotone</a>.</p>
<p>The current source is available in <a href="{{ site_url('develop/monotone') }}">monotone</a>.</p>
<h2>Additional Information</h2>
<p>