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

add iMule and tahoe-lafs to the list

Browse Source
This commit is contained in:
m1xxy
2011-06-17 19:33:43 +00:00
parent addb54b504
commit 839f3b4624
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
www.i2p2/pages/techintro.html
View File

@@ -41,11 +41,13 @@
<ul> <ul>
<li>Web browsing: using any existing browser that supports using a proxy.</li> <li>Web browsing: using any existing browser that supports using a proxy.</li>
<li>Chat: IRC, Jabber, <a href="#app.i2pmessenger">I2P-Messenger</a>.</li> <li>Chat: IRC, Jabber, <a href="#app.i2pmessenger">I2P-Messenger</a>.</li>
<li>File sharing: <a href="#app.i2psnark">I2PSnark</a>, <a href="#app.robert">Robert</a>, <li>File sharing: <a href="#app.i2psnark">I2PSnark</a>, <a href="#app.robert">Robert</a>, <a href="#app.imule">iMule</a>
<a href="#app.i2phex">I2Phex</a>, <a href="#app.pybit">PyBit</a>, <a href="#app.i2pbt">I2P-bt</a> <a href="#app.i2phex">I2Phex</a>, <a href="#app.pybit">PyBit</a>, <a href="#app.i2pbt">I2P-bt</a>
and others. and others.
</li> </li>
<li>E-mail: <a href="#app.i2pmail">susimail</a> and <a href="#app.i2pbote">I2P-Bote</a>.</li> <li>E-mail: <a href="#app.i2pmail">susimail</a> and <a href="#app.i2pbote">I2P-Bote</a>.</li>
<li>Blog: using e.g. the pebble plugin or the distributed blogging software <a href="#app.syndie">Syndie</a>.</li>
<li>Distributed Data Store: Save your data redundantly in the Tahoe-LAFS cloud over I2P.</li>
<li>Newsgroups: using any newsgroup reader that supports using a proxy.</li> <li>Newsgroups: using any newsgroup reader that supports using a proxy.</li>
</ul> </ul>
<p> <p>
@@ -82,7 +84,7 @@
making use of a few cryptographic routines under BSD-style licenses. The people making use of a few cryptographic routines under BSD-style licenses. The people
working on I2P do not control what people release client applications under, working on I2P do not control what people release client applications under,
and there are several GPL'ed applications available (<a href="#app.i2ptunnel">I2PTunnel</a>, and there are several GPL'ed applications available (<a href="#app.i2ptunnel">I2PTunnel</a>,
<a href="#app.i2pmail">susimail</a>, <a href="#app.i2psnark">I2PSnark</a>, <a href="#app.i2pmail">susimail</a>, <a href="#app.i2psnark">I2PSnark</a>, <a href="#app.i2pbote">I2P-Bote</a>,
<a href="#app.i2phex">I2Phex</a> and others.). <a href="#app.i2phex">I2Phex</a> and others.).
<a href="http://www.i2p.net/halloffame">Funding</a> for I2P comes entirely from donations, <a href="http://www.i2p.net/halloffame">Funding</a> for I2P comes entirely from donations,
and does not receive any tax breaks in any jurisdiction at this time, and does not receive any tax breaks in any jurisdiction at this time,
@@ -850,7 +852,7 @@ href="http://www.klomp.org/snark/">Snark</a> client</i></p>
run entirely on top of I2P. While it has disabled some of Phex's functionality, run entirely on top of I2P. While it has disabled some of Phex's functionality,
such as integration with Gnutella webcaches, the basic file sharing and chatting such as integration with Gnutella webcaches, the basic file sharing and chatting
system is fully functional. </p> system is fully functional. </p>
<h2 id="app.i2phex">iMule</h2> <h2 id="app.i2mule">iMule</h2>
<p><i>Developed by: mkvore</i></p> <p><i>Developed by: mkvore</i></p>
<p> iMule is a fairly direct port of the aMule filesharing client <p> iMule is a fairly direct port of the aMule filesharing client
running entirely inside I2P.</p> running entirely inside I2P.</p>