i2p.itoopie/readme.html

<div align="right">
<div class="langbox" align="right"><a href="/index.jsp?lang=en"><img src="/flags.jsp?c=us" title="English" alt="English"></a> <a href="/index.jsp?lang=zh"><img src="/flags.jsp?c=cn" title="Chinese" alt="Chinese"></a> <a href="/index.jsp?lang=de"><img src="/flags.jsp?c=de" title="Deutsch" alt="Deutsch"></a> <a href="/index.jsp?lang=fr" title="Fran&ccedil;ais" alt="Fran&ccedil;ais"><img src="/flags.jsp?c=fr"></a> <a href="/index.jsp?lang=nl"><img src="/flags.jsp?c=nl" title="Nederlands" alt="Nederlands"></a> <a href="/index.jsp?lang=sv"><img src="/flags.jsp?c=se" title="Svenska" alt="Svenska"></a></div>
</div>
<h2>Welcome to I2P!</h2>
<p>If you've just started I2P, the Active: numbers on the left should start to
grow over the next few minutes and you'll see a "shared clients" local destination listed
on the left (if not, <a href="#trouble">see below</a>). Once those show up, you can:
<ul>
 <li><b>browse "eepsites"</b> - on I2P there are anonymously hosted websites - 
     tell your browser to use the <b>HTTP proxy at localhost port 4444</b>, then
     browse to an eepsite:<br />
<ul class="links">
         <li class="tidylist"><a href="http://inproxy.tino.i2p/status.php">inproxy.tino.i2p</a> and
             <a href="http://perv.i2p/stats.cgi">perv.i2p</a>: sites tracking active eepsites</li>
         <li class="tidylist"><a href="http://forum.i2p/">forum.i2p</a>: a secure and anonymous connection to <a href="http://forum.i2p2.de/">forum.i2p2.de</a></li>
         <li class="tidylist"><a href="http://www.i2p2.i2p/">www.i2p2.i2p</a> and mirror <a href="http://i2p-projekt.i2p">i2p-projekt.i2p</a>:
              secure and anonymous connections to <a href="http://www.i2p2.de/">www.i2p2.de</a></li>
         <li class="tidylist"><a href="http://eepsites.i2p/">eepsites.i2p</a>: an anonymously hosted search engine of eepsites</li>
         <li class="tidylist"><a href="http://ugha.i2p/">ugha.i2p</a>: ugha's eepsite, a wiki that anyone can edit, and lots of links</li>
         <li class="tidylist"><a href="http://fproxy.tino.i2p">fproxy.tino.i2p</a>: Freenet proxy</li>
	 <li class="tidylist"><a href="http://echelon.i2p">echelon.i2p</a>: software archive and information for I2P</li></p>
There are many more eepsites - just follow the links from the ones you see,
     bookmark your favorites, and visit them often!</ul><br /><br /><ul>
 <li class="tidylist"><b>browse the web</b> - there is currently an HTTP "outproxy" in I2P hooked
     up to your own HTTP proxy on port 4444 - simply set your browser's proxy to
     use it (as above) and go to any normal URL - your requests will be bounced
     through the I2P network.</li>
 <li class="tidylist"><b>transfer files</b> - there is an integrated <a href="i2psnark/">port</a> of the
     <a href="http://www.klomp.org/snark/">Snark</a> <a href="http://www.bittorrent.com/">BitTorrent</a>
     client.</li>
 <li class="tidylist"><b>use anonymous email</b> - postman has created a mail system compatible with normal mail
     clients (POP3 / SMTP) that allows email within I2P as well as mail from and to the normal
     internet!  get your account at <a href="http://hq.postman.i2p/">hq.postman.i2p</a>.
     We bundle <a href="/susimail/susimail">susimail</a>,
     a web based anonymity-oriented pop3/smtp client configured to access postman's mail services.</li>
 <li class="tidylist"><b>chat anonymously</b> - fire up your own IRC client and connect to the 
     server at <b>localhost port 6668</b>.  This points at one of two anonymously hosted
     IRC servers, but neither you nor they know where the other is.</li>
 <li class="tidylist"><b>blog anonymously</b> - check out <a href="http://syndie.i2p2.de/">Syndie</a></li>
 <li class="tidylist">and lots more</li>
</ul>
<h2>Want your own eepsite?</h2>

<p>We've bundled some software to let you run your own eepsite - a 
<a href="http://jetty.mortbay.org/">Jetty</a> instance listening on 
<a href="http://localhost:7658/">http://localhost:7658/</a>.  Simply place your files in
the <code>eepsite/docroot/</code> directory (or place any standard JSP/Servlet <code>.war</code>
files under <code>eepsite/webapps</code>, or standard CGI script under <code>eepsite/cgi-bin</code>) 
and they'll show up.  After starting up an <a href="/i2ptunnel/">eepsite tunnel</a> pointing at it, your eepsite
will be visible to others.
Detailed instructions for starting your eepsite are on
<a href="http://localhost:7658/">your temporary eepsite page</a>.
</p>
<!-- 
<p>
If you wish to register your eepsite with a unique top level domain (eg. http://bobsplace.i2p) making it visible on the network, you 
can do so here: <a href="http://stats.i2p/i2p/addkey.html">http://stats.i2p/i2p/addkey.html</a>
</p>
-->

<h2><a name="trouble">Troubleshooting</a></h2>

<p>Be patient - I2P may be slow to start the first time as it searches for peers.
If, after 30 minutes, your Active: connected/recent count has less than 10 connected
peers, you should open port 8887 on your firewall for better connectivity.
If you cannot see any eepsites at all (even <a href="http://www.i2p2.i2p/">www.i2p2.i2p</a>),
be sure your browser proxy is set to localhost port 4444.
You may also want to review the information on the 
<a href="http://www.i2p2.i2p/">I2P website</a>, post up messages to the 
<a href="http://forum.i2p2.de/">I2P discussion forum</a>, or swing by #i2p or
#i2p-chat on IRC at <a href="irc://irc.freenode.net/#i2p">irc.freenode.net</a>, irc.postman.i2p or irc.freshcoffee.i2p (they're linked together).</p>
<hr />