forked from I2P_Developers/i2p.www
merge of '3de18dfd8ce712e642a0ef0b59959d919a02e44a'
and '59a1ace8a395a66b481c7b453660428e110151e2'
This commit is contained in:
@ -482,34 +482,34 @@ Contact us if you would like to help.
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://syndie.i2p2.de/">Syndie</a>
|
||||
<li>
|
||||
</li><li>
|
||||
<a href="http://forum.i2p/viewforum.php?f=25">I2Phex</a> - contact Complication
|
||||
<a href="http://forum.i2p2.de/viewforum.php?f=25">(outside I2P)</a>
|
||||
<li>
|
||||
</li><li>
|
||||
<a href="http://www.imule.i2p/">IMule</a>
|
||||
<li>I2PRufus - contact codevoid
|
||||
<li>I2P-BT - contact sponge
|
||||
<li>BOB - contact sponge
|
||||
</ul>
|
||||
</li><li>I2PRufus - contact codevoid
|
||||
</li><li>I2P-BT - contact sponge
|
||||
</li><li>BOB - contact sponge
|
||||
</li></ul>
|
||||
|
||||
<h2>Application Ideas</h2>
|
||||
<ul>
|
||||
<li>NNTP server - there have been some in the past, none at the moment
|
||||
<li>Jabber server - there have been some in the past, none at the moment
|
||||
<li>PGP Key server and/or proxy
|
||||
<li>Download manager / eepget scheduler -
|
||||
</li><li>Jabber server - there have been some in the past, none at the moment
|
||||
</li><li>PGP Key server and/or proxy
|
||||
</li><li>Download manager / eepget scheduler -
|
||||
We use eepget to fetch lots of things reliably over i2p, and there's already an
|
||||
implementation of a sequential download manager (net.i2p.util.EepGetScheduler),
|
||||
but there isn't any sort of user interface to it. A web based UI would be
|
||||
great.
|
||||
<li>Content Distribution / DHT applications - help out with <a href="http://feedspace.i2p/">feedspace</a>,
|
||||
</li><li>Content Distribution / DHT applications - help out with <a href="http://feedspace.i2p/">feedspace</a>,
|
||||
port dijjer, look for alternatives
|
||||
<li>Help out with <a href="http://syndie.i2p2.de/">Syndie</a> development
|
||||
<li>Web-based applications - The sky is the limit for hosting web-server-based
|
||||
</li><li>Help out with <a href="http://syndie.i2p2.de/">Syndie</a> development
|
||||
</li><li>Web-based applications - The sky is the limit for hosting web-server-based
|
||||
applications such as blogs, pastebins, storage, tracking, feeds, etc.
|
||||
Any web or CGI technology such as Perl, PHP, Python, or Ruby will work.
|
||||
<li>Resurrect some old apps - in the i2p source package -
|
||||
</li><li>Resurrect some old apps - in the i2p source package -
|
||||
bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
{% endblock %}
|
||||
|
@ -92,7 +92,7 @@ etc), and the like.</p>
|
||||
<td><p>duck, smeghead</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td> <p><b><a href="bounty_rutrans">translation into Russian</a></b></td>
|
||||
<td> <p><b><a href="bounty_rutrans">translation into Russian</a></b></p></td>
|
||||
<td><p>claimed for $230 USD sponsored by russian sponsor</p></td>
|
||||
<td><p>4get</p></td>
|
||||
</tr>
|
||||
|
@ -44,9 +44,9 @@
|
||||
Here are some places, pick one or more.
|
||||
<ul>
|
||||
<li><a href="http://trac.i2p2.de/report/1">trac.i2p2.de</a> ticket (preferred method)
|
||||
<li><a href="http://paste.i2p2.i2p/">paste.i2p2.i2p</a> and follow up on IRC #i2p
|
||||
<li>Discuss with the developers on IRC #i2p
|
||||
</ul>
|
||||
</li><li><a href="http://paste.i2p2.i2p/">paste.i2p2.i2p</a> and follow up on IRC #i2p
|
||||
</li><li>Discuss with the developers on IRC #i2p
|
||||
</li></ul>
|
||||
</p>
|
||||
<p>
|
||||
Please include relevant information from the router logs and wrapper logs.
|
||||
@ -72,9 +72,9 @@ Presence on this list does not imply endorsement.
|
||||
<div class="links">
|
||||
<ul>
|
||||
<li><a href="http://i2host.i2p/cgi-bin/i2hostetag">http://i2host.i2p/cgi-bin/i2hostetag</a>
|
||||
<li><a href="http://stats.i2p/cgi-bin/newhosts.txt">http://stats.i2p/cgi-bin/newhosts.txt</a>
|
||||
<li><a href="http://tino.i2p/hosts.txt">http://tino.i2p/hosts.txt</a>
|
||||
</ul>
|
||||
</li><li><a href="http://stats.i2p/cgi-bin/newhosts.txt">http://stats.i2p/cgi-bin/newhosts.txt</a>
|
||||
</li><li><a href="http://tino.i2p/hosts.txt">http://tino.i2p/hosts.txt</a>
|
||||
</li></ul>
|
||||
</div>
|
||||
</p>
|
||||
|
||||
@ -103,28 +103,28 @@ There are many possible causes of high CPU usage. Here is a checklist:
|
||||
<li>
|
||||
Are you using Sun Java or some other version? (type java -version at a command prompt to find out)
|
||||
We have several reports of high CPU usage when using other Java versions.
|
||||
<li>
|
||||
</li><li>
|
||||
Are you running a BitTorrent client over i2p? Try reducing the number of torrents, the bandwidth limits,
|
||||
or try turning it off completely to see if that helps.
|
||||
<li>
|
||||
</li><li>
|
||||
Are your bandwidth limits too high? Perhaps too much traffic is going through your
|
||||
computer, and it is overloaded. Try reducing share bandwidth percentage on config.jsp.
|
||||
<li>
|
||||
</li><li>
|
||||
Are you running the latest version of I2P? Recent versions have several performance improvements
|
||||
and bug fixes.
|
||||
<li>
|
||||
</li><li>
|
||||
Have you configured I2P with enough memory? Look at the memory graph on graphs.jsp to see
|
||||
if the memory usage is "pegged", which means the JVM is spending most of its time in
|
||||
garbage collection. Increase the wrapper.java.maxmemory setting in wrapper.config.
|
||||
<li>
|
||||
</li><li>
|
||||
Is the CPU usage simply higher than you would like, or is it pegged at 100% for a long time?
|
||||
If it's pegged, this could be a bug. Look in the logs for clues.
|
||||
<li>
|
||||
</li><li>
|
||||
You may be using the Java-based BigInteger library instead of the native version,
|
||||
especially if you are running on a new or unusual OS or hardware (64-bit, OS X, OpenSolaris, etc.).
|
||||
See the <a href="jbigi.html">jbigi page</a> for instructions on
|
||||
diagnosing, building, and testing methods.
|
||||
<li>
|
||||
</li><li>
|
||||
If your native jbigi library is working fine, the biggest user of
|
||||
CPU may be routing traffic for participating tunnels. This uses CPU
|
||||
because at each hop a layer of encryption must be decoded.
|
||||
@ -133,7 +133,7 @@ share bandwidth on
|
||||
<a href="http://localhost:7657/config.jsp">config.jsp</a>,
|
||||
or by setting <tt>router.maxParticipatingTunnels=nnn</tt> on
|
||||
<a href="http://localhost:7657/configadvanced.jsp">configadvanced.jsp</a>.
|
||||
</ul>
|
||||
</li></ul>
|
||||
|
||||
<h3 id="content">I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?
|
||||
<span class="permalink">(<a href="#content">link</a>)</span></h3>
|
||||
@ -151,12 +151,12 @@ Your only alternative is to refuse to route
|
||||
<i>any</i> traffic, by setting your share bandwidth or maximum participating tunnels to 0 (see above).
|
||||
It would be nice if you didn't do this, you should help the network by routing traffic for others.
|
||||
Over 95% of users route traffic for others.
|
||||
<li><b>Storage</b> - I2P does not do distributed storage of content. You must be thinking of
|
||||
</li><li><b>Storage</b> - I2P does not do distributed storage of content. You must be thinking of
|
||||
<a href="http://freenetproject.org/">Freenet</a>.
|
||||
You are not storing anybody else's content.
|
||||
<li><b>Access</b> - If there are some eepsites you don't like, don't go there.
|
||||
</li><li><b>Access</b> - If there are some eepsites you don't like, don't go there.
|
||||
Or, use a blocking proxy like Privoxy or some type of "net nanny".
|
||||
</ul>
|
||||
</li></ul>
|
||||
</p>
|
||||
|
||||
<h3 id="vary">My active peers / known peers / participating tunnels / connections / bandwidth vary dramatically over time! Is anything wrong?
|
||||
@ -239,7 +239,7 @@ The best way to stay "better-connected" to the network is to share more bandwidt
|
||||
If you would like to set up some type of outproxy, carefully research the potential risks.
|
||||
The I2P community may or may not be able to help with the technical aspects, feel free to ask.
|
||||
</p><p>
|
||||
<b><l>Update</b></l>: Thanks to h2ik and mer'd, they provide service to demonstrate i2p's capability to support https outproxy.
|
||||
<b><l>Update</l></b>: Thanks to h2ik and mer'd, they provide service to demonstrate i2p's capability to support https outproxy.
|
||||
the client side setup is not hard at all, if you follow the instruction strictly ;) :
|
||||
<ol><li>Open <a href="http://localhost:7657/i2ptunnel/index.jsp">i2p tunnel manager</a>. Scroll down to the bottom.
|
||||
</li><li>Choose <b>CONNECT</b> from <b>New Client Tunnel</b> dropdown list, click <b>Create</b>
|
||||
@ -560,14 +560,14 @@ router advanced configuration option <tt>i2cp.tcp.bindAllInterfaces=true</tt> an
|
||||
<p>
|
||||
To reseed an I2P router manually, do the following:
|
||||
<ul>
|
||||
<li>Stop your I2P router</li>
|
||||
<li>Open <a href="http://i2pdb.tin0.de/netDb/">http://i2pdb.tin0.de/netDb/</a> or
|
||||
<a href="http://netdb.i2p2.de/">http://netdb.i2p2.de/</a> using a web browser</li>
|
||||
<li>Save a dozen "routerInfo" files to your I2P "netDb" directory (ignore the "leaseSet" files)</li>
|
||||
<li>Alternate method (easier): Download <a href="http://i2pdb.tin0.de/latest.zip">http://i2pdb.tin0.de/latest.zip</a>
|
||||
<li>Stop your I2P router
|
||||
</li><li>Open <a href="http://i2pdb.tin0.de/netDb/">http://i2pdb.tin0.de/netDb/</a> or
|
||||
<a href="http://netdb.i2p2.de/">http://netdb.i2p2.de/</a> using a web browser
|
||||
</li><li>Save a dozen "routerInfo" files to your I2P "netDb" directory (ignore the "leaseSet" files)
|
||||
</li><li>Alternate method (easier): Download <a href="http://i2pdb.tin0.de/latest.zip">http://i2pdb.tin0.de/latest.zip</a>
|
||||
and unzip it into your I2P "netDb" directory.
|
||||
<li>Start your I2P router</li>
|
||||
</ul>
|
||||
</li><li>Start your I2P router
|
||||
</li></ul>
|
||||
</p>
|
||||
|
||||
<hr />
|
||||
|
@ -14,39 +14,39 @@ Here's a list to help you get started!
|
||||
Tell people about I2P on forums, blogs, and comments to articles.
|
||||
Fix up the Wikipedia article about I2P in your language.
|
||||
Tell your friends.
|
||||
<li><b>Testing</b> -
|
||||
</li><li><b>Testing</b> -
|
||||
Run the latest builds from <a href="monotone.html">monotone</a>
|
||||
and report results on #i2p or as bugs on <a href="http://trac.i2p2.de/report/1">Trac</a>.
|
||||
<li><b>Documentation</b> -
|
||||
</li><li><b>Documentation</b> -
|
||||
Help fix the parts of the website that are outdated or incomplete.
|
||||
Translate pages into other languages.
|
||||
<li><b>Pictures</b> -
|
||||
</li><li><b>Pictures</b> -
|
||||
Make some more pictures, fix the old ones on the website
|
||||
<li><b>Content</b> -
|
||||
</li><li><b>Content</b> -
|
||||
Make an eepsite! Add some content! Contribute to the community!
|
||||
<li><b>Services</b> -
|
||||
</li><li><b>Services</b> -
|
||||
Run a service on an eepsite. It could be a proxy, a forum, a tracker,
|
||||
a naming service, a search engine, an eepsite monitor... many of these
|
||||
aren't that hard.
|
||||
<li><b>Applications</b> -
|
||||
</li><li><b>Applications</b> -
|
||||
Write or port applications for I2P! There's some guidelines and
|
||||
a list of ideas on the <a href="applications.html">applications page</a>.
|
||||
<li><b>Coding</b> -
|
||||
</li><li><b>Coding</b> -
|
||||
There's plenty to do if you know Java or are ready to learn.
|
||||
Check for open tickets on <a href="http://trac.i2p2.de/report/1">Trac</a>
|
||||
or the TODO list on <a href="http://zzz.i2p/">zzz.i2p</a> for
|
||||
some ideas on where to start.
|
||||
See the <a href="newdevelopers.html">new developer's guide</a> for details.
|
||||
<li><b>Translation</b> -
|
||||
</li><li><b>Translation</b> -
|
||||
Help translate the website and the software into your language.
|
||||
See the <a href="newtranslators.html">new translator's guide</a> for details.
|
||||
<li><b>Analysis</b> -
|
||||
</li><li><b>Analysis</b> -
|
||||
Study or test the code to look for vulnerabilities.
|
||||
Both anonymity vulnerabilities from the various
|
||||
<a href="how_threatmodel.html">threat models</a>,
|
||||
and DOS and other weaknesses due to securities holes,
|
||||
need researching.
|
||||
<li><b><a href="donate.html">Donate</a></b>
|
||||
</li><li><b><a href="donate.html">Donate</a></b>
|
||||
|
||||
</ol>
|
||||
</li></ul>
|
||||
{% endblock %}
|
||||
|
@ -24,7 +24,7 @@
|
||||
<!--
|
||||
<td>
|
||||
<a href="download"><img src="/_static/images/logo07c.jpg" alt="0.7 logo" border="none"/></a> -->
|
||||
</table>
|
||||
</td></tr></table>
|
||||
<div class="underline"></div>
|
||||
<p>I2P is an anonymizing network, offering a simple layer that identity-sensitive
|
||||
applications can use to securely communicate. All data is wrapped with several
|
||||
|
Reference in New Issue
Block a user