686742a67bf8eef2bc0f7f48c8f2de68028921af

* Inlined the Syndie CSS to reduce the number of HTTP requests (and because firefox [and others?] delay rendering until they fetch the css). * Make sure we fire the shutdown tasks when regenerating a new identity (thanks picsou!) * Cleaned up some of the things I b0rked in the 'dynamic keys' mode * Don't drop SSU sessions if they're still transmitting data successfully, even if there are transmission failures * Adjusted the time summarization to display hours after 119m, not 90m * Further EepGet cleanup (grr)
<p>If you've just started I2P, the Active: number on the left should start to grow over the next few minutes and you'll see some local "destinations" listed on the left (if not, <a href="#trouble">see below</a>). Once those show up, you can:</p> <ul> <li><b>blog anonymously</b> - check out <a href="/syndie/">Syndie</a></li> <li><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><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 - <ul> <li><a href="http://orion.i2p/">orion.i2p</a>: a site which tracks eepsite uptime and changes</li> <li><a href="http://forum.i2p/">forum.i2p</a>: a secure and anonymous connection to <a href="http://forum.i2p.net/">forum.i2p.net</a></li> <li><a href="http://www.i2p/">www.i2p</a>: a secure and anonymous connection to <a href="http://www.i2p.net/">www.i2p.net</a></li> <li><a href="http://search.i2p/">search.i2p</a>: an anonymously hosted search engine of eepsites</li> <li><a href="http://ugha.i2p/">ugha.i2p</a>: ugha's eepsite, a wiki that anyone can edit, and lots of links</li> <li><a href="http://dev.i2p/">dev.i2p</a>: a secure and anonymous connection to <a href="http://dev.i2p.net/">dev.i2p.net</a></li> <li>Freenet proxies: <a href="http://fproxy.i2p/">fproxy.i2p</a> and <a href="http://fproxy.tino.i2p">fproxy.tino.i2p</a></li> </ul> There are many more eepsites - just follow the links from the ones you see, bookmark your favorites, and visit them often!</li> <li><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><b>transfer files</b> - there is an <a href="http://i2p-bt.postman.i2p/">I2P port</a> of the <a href="http://www.bittorrent.com/">BitTorrent</a> application available.</li> <li><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="http://susi.i2p/">Susi's</a> <a href="/susimail/susimail">susimail</a>, a web based anonymity-oriented pop3/smtp client configured to access postman's mail services.</li> <li>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. Your eepsite's <i>destination</i> (which uniquely and securely identifies it) is shown on the I2PTunnel <a href="/i2ptunnel/">configuration page</a> - if you want other people to see your eepsite, you need to give them that really huge string. Just paste it into the <a href="http://forum.i2p/viewforum.php?f=16">Eepsite announce</a> forum, add it to ugha's <a href="http://ugha.i2p/I2pLinks">wiki</a>, <a href="http://orion.i2p/">orion's list</a>, or paste it in the #i2p or #i2p-chat channels on IRC (be sure to split it into two lines, as its too long for one).</p> <h2><a name="trouble">Troubleshooting</a></h2> <p>If the left hand side has a warning, telling you to check your NAT or firewall, please see the <a href="/config.jsp">config page</a> and make sure that you can receive <b>inbound TCP and UDP connections on port 8887</b> (or another port that you specify). Problems forwarding that port account for the vast majority of issues people run into. When it says "Active: 72/85", the "72" means how many peers you are connected with now, and "85" means how many you have spoken with recently - if that first number is 0, you can bet that there are firewall issues. If the second number is under 5, you should reseed (a link on the left hand side of the page will show up to help you when necessary).</p> <p>If you are still having problems, you may want to review the information on the <a href="http://www.i2p.net/">I2P website</a>, post up messages to the <a href="http://forum.i2p.net/">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> <p><b>As a note, you can change this page by editing the file "docs/readme.html"</b></p>
Description
Languages
Java
96.6%
Shell
1.5%
HTML
1.4%
Dockerfile
0.3%
AIDL
0.2%