caps (thanks bar)

This commit is contained in:
jrandom
2005-10-05 01:11:25 +00:00
committed by zzz
parent 0c0e269e72
commit 4a49e98c31

View File

@ -17,7 +17,7 @@ pre { font-size: 10; font-family: sans-serif }
<center>
<b class="title">Introducing I2P</b><br />
<span class="subtitle">a scalable framework for anonymous communication</span><br />
<i style="font-size: 8">$Id: techintro.html,v 1.4 2005/10/04 18:34:19 jrandom Exp $</i>
<i style="font-size: 8">$Id: techintro.html,v 1.5 2005/10/04 19:52:27 jrandom Exp $</i>
<br />
<br />
@ -64,7 +64,7 @@ route mixnet, allowing them to blend their activity with the larger anonymity se
users already running on top of I2P. Applications available already provide the full
range of typical Internet activities - anonymous web browsing, anonymous web hosting,
anonymous blogging (with <a href="#app.syndie">Syndie</a>), anonymous chat (via IRC or
jabber), anonymous swarming file transfers (with <a href="#app.i2pbt">i2p-bt</a> and
Jabber), anonymous swarming file transfers (with <a href="#app.i2pbt">i2p-bt</a> and
<a href="#app.azneti2p">Azureus</a>), anonymous file sharing (with
<a href="#app.i2phex">I2Phex</a>), anonymous email (with <a href="#app.i2pmail">I2Pmail</a>
and <a href="#app.i2pmail">susimail</a>), anonymous newsgroups, as well as several
@ -134,7 +134,7 @@ with individual applications. The fact that someone is running I2P is not usual
a secret. What is hidden is information on what the user is doing, if anything at
all, as well as what router a particular destination is connected to. End users
will typically have several local destinations on their router - for instance, one
proxying in to irc servers, another supporting the user's anonymous webserver ("eepsite"),
proxying in to IRC servers, another supporting the user's anonymous webserver ("eepsite"),
another for an I2Phex instance, another for torrents, etc.
</p>