add links to reseed research and tools on reseed page

This commit is contained in:
idk
2021-09-22 23:34:23 -04:00
parent 8464cbb992
commit 457ecc2286

View File

@@ -8,29 +8,54 @@
<h2 id="about">{% trans %}About Reseed hosts{% endtrans %}</h2>
<p>{% trans -%}
Reseed hosts are needed to for bootstrapping, that is, providing the initial set of I2P nodes for your I2P node to talk to. Depending on the status of your node it may need to bootstrap every now and then if many of the nodes it knows of aren't contactable.
Reseed hosts are needed to for bootstrapping, that is, providing the initial set
of I2P nodes for your I2P node to talk to. Depending on the status of your node
it may need to bootstrap every now and then if many of the nodes it knows of
aren't contactable.
{%- endtrans %}</p>
<p>{% trans -%}
Reseeding is done over an encrypted connection and all of the bootstrap information is signed by the reseed host you connect to, making it impossible for an unauthenticated source to provide you with false information.
Reseeding is done over an encrypted connection and all of the bootstrap
information is signed by the reseed host you connect to, making it impossible
for an unauthenticated source to provide you with false information.
{%- endtrans %}</p>
<h2 id="running">{% trans %}Running a Reseed host{% endtrans %}</h2>
<p>
{% trans -%}
The more reseed hosts that are run, the more resilient the I2P network becomes, and the harder it is to prevent users of I2P from connecting to the network.
{% trans -%}Operating a reseed server can be accessible to any sysadmin familiar
with I2P, and we encourage new reseed operators to get in contact with us at
<a href="http://zzz.i2p">the development forums</a>. The more reseed hosts that
are run, the more resilient the I2P network becomes, and the harder it is to
prevent users of I2P from connecting to the network.
{%- endtrans %}
</p>
{% trans -%}
There have also been cases where the reseed hosts we had, have been under heavy load due to botnet activities.
{%- endtrans %}
</p>
<p>
<a href="{{ site_url('get-involved/guides/reseed') }}">How to run a Reseed host</a>
</p>
<h2 id="thank you">{% trans %}Thank you{% endtrans %}</h2>
<ul>
<li><a href="{{ site_url('get-involved/guides/reseed') }}">Reseed Contributors Guide</a></li>
<li><a href="https://i2pgit.org/idk/reseed-tools">Reseed Software and Documentation</a></li>
</ul>
<h2 id="other">{% trans %}Other ways of Reseeding{% endtrans %}</h2>
<p>
{% trans -%}
In order to make I2P more reslient, other kinds of reseeding are possible. One
important way of carrying out a reseed is the file-based reseed, where a user
with a running I2P router generates a reseed file for a friend and transfers it
to them as a .zip file. Others use cloud-based infrastructure to resist
censorship. These reseed methods provide functionality which aids people in
situations where reseeds are restricted.
{%- endtrans %}
</p>
<ul>
<li><a href="{{ site_url('blog/post/2020/06/07/file-based-reseed') }}">File Based Reseed</a></li>
<li><a href="https://homepage.np-tokumei.net/post/notes-i2p-reseed-over-cloudflare/">I2P Reseed over Cloudflare</a></li>
<li><a href="https://homepage.np-tokumei.net/post/notes-censorship-resistant-i2p-reseeding/">Censorship Resistant I2P Reseeding</a></li>
</ul>
<h2 id="thank you">{% trans %}Thank you Reseed Operators{% endtrans %}</h2>
<p>
{%-trans -%}
If you are running a reseed server, We would like to thank you for helping to