diff --git a/i2p2www/pages/papers/anonbib.bib b/i2p2www/pages/papers/anonbib.bib
index 0148d0f21c98e5b6a12f09ab27ff9e7249a61e50..6ab5ccacbce3065155aeb7df88717dd5516e954f 100644
--- a/i2p2www/pages/papers/anonbib.bib
+++ b/i2p2www/pages/papers/anonbib.bib
@@ -108,7 +108,7 @@
school = {University of Amsterdam},
year = {2018},
month = {June},
- www_pdf_url = {https://delaat.net/rp/2017-2018/p97/report.pdf},
+ www_pdf_url = {https://docslib.org/doc/12313748/blockchain-based-sybil-attack-mitigation-a-case-study-of-the-i2p},
www_section = comm,
}
@@ -239,7 +239,7 @@ services, namely Tor, JonDonym, and I2P as case studies; and
(iii) present a mechanism to evaluate anonymity services based
on our factors and measure the level of anonymity.}},
keywords = {Anonymity Factors ; Metrics ; Tor ; I2P ; JonDonym},
- www_pdf_url = {https://www.cs.dal.ca/sites/default/files/technical_reports/CS-2017-01.pdf},
+ www_pdf_url = {https://cdn.dal.ca/content/dam/dalhousie/pdf/faculty/computerscience/technical-reports/CS-2017-01.pdf},
www_section = comm,
}
@@ -249,7 +249,7 @@ on our factors and measure the level of anonymity.}},
booktitle = {Proceedings of the 38th IEEE Symposium on Security and Privacy Workshops, 2nd International Workshop on Traffic Measurements for Cybersecurity (WTMC 2017)},
year = {2017},
month = {May},
- www_pdf_url = {https://www.cs.dal.ca/sites/default/files/technical_reports/cs-2017-04.pdf},
+ www_pdf_url = {https://www.researchgate.net/publication/321999503_Effects_of_Shared_Bandwidth_on_Anonymity_of_the_I2P_Network_Users},
www_section = traffic,
}
@@ -277,7 +277,7 @@ that presents I2P Observer, a software to collect information about I2P and one
possibilities on I2P.}},
note = {Title : Analysis of the I2P Network. School: Bern University of Applied Sciences - Department of Computer Science},
www_section = traffic,
- www_pdf_url = {https://jenix.net/i2p-observer/Analysis_of_the_I2P_Network-Bachelor_Thesis.pdf},
+ www_pdf_url = {https://docslib.org/doc/6144412/analysis-of-the-i2p-network-information-gathering-and-attack-evaluations},
}
@inproceedings{jeong2016,
@@ -301,7 +301,7 @@ that a large number of queries are observed and outlining
various potential directions of addressing such leakage.}},
keywords = {I2P, DNS, privacy, security, network analysis},
www_section = traffic,
- www_pdf_url = {https://www.cse.buffalo.edu/~mohaisen/doc/16-sigcomm.pdf},
+ www_pdf_url = {https://www.cs.ucf.edu/~mohaisen/doc/sigcomm16.pdf},
pages = {557--558},
}
@@ -567,7 +567,7 @@ networks},
howpublished = {Seminar, Humboldt University of Berlin},
year = {2011},
month = {November},
- www_pdf_url = {http://userpage.fu-berlin.de/~semu/docs/2011_seminar_ehlert_i2p.pdf},
+ www_pdf_url = {https://www.freehaven.net/anonbib/cache/ehlert2011:usability-comparison-i2p-tor.pdf},
www_section = comm,
}
@@ -651,7 +651,7 @@ networks},
abstract={{Today, to be monitored while surfing the web seems to be a natural act and thus tools and applications to achieve online anonymity are more important than ever. The usability of such a tool plays not only a prominent role for each single user; in the area of anonymization networks it usually holds that the protection for every single user is higher, the more users participate. Hence, usability is of great importance, since bad usability decreases the number of potential users. In this paper we examine the usability of four software implementations for anonymous communication techniques especially with regards to the installation procedure. The usability is evaluated with the help of cognitive walk-throughs. We also inspect the quality of service of these implementations by means of a performance test.}},
keywords={Internet;security of data;anonymity networks;anonymization networks;anonymous communication techniques;cognitive walk-throughs;installation;quality of service;software implementations;usability inspection;Communication system security;Inspection;Monitoring;Operating systems;Privacy;Quality management;Quality of service;System testing;Technology management;Usability;AN.ON;Anonymity;HCI;JAP;JonDo;JondoNym;Tor;Usability},
doi={10.1109/CONGRESS.2009.38},
- www_pdf_url = {http://pimenidis.org/research/papers/usability-inspection.pdf},
+ www_pdf_url = {https://www.researchgate.net/publication/224084986_Usability_Inspection_of_Anonymity_Networks},
www_section = comm,
}
diff --git a/i2p2www/pages/site/about/software.html b/i2p2www/pages/site/about/software.html
index 385a8fef49dddcc6b7ac34be393703d8fae5832c..8266b5244db0f0fd270959f5b7015b862490dd8d 100644
--- a/i2p2www/pages/site/about/software.html
+++ b/i2p2www/pages/site/about/software.html
@@ -3,14 +3,12 @@
{% block content %}
<h1>{{ _('The I2P Software') }} (I2P)</h1>
-<p>{% trans %}When you install the I2P software made available at geti2p.net, you are
-actually installing an I2P router and an accompanying bundle of basic
-applications. The I2P Java distribution is the first I2P software gateway and
-has been actively developed since 2003.{%- endtrans %}</p>
-<p>{% trans %}The applications are made available through a webUI, which listens at
-127.0.0.1:7657, and the main page of which is called the “Router Console,â€
-where you monitor the health of your connection to the network and access
-applications to use on the network.{%- endtrans %}</p>
+<p>{% trans %The I2P Java distribution is the first I2P software gateway and
+has been actively developed since 2003. It includes a router, applications, and the ability to manage and customize your own connection with the I2P network using a built in Hidden Services manager{%- endtrans %}</p>
+<p>{% trans %}Applications are made available through a webUI that listens at
+127.0.0.1:7657. The main page is called the “Router Console,â€
+where network connection status is displayed and access
+to applications is provided.{%- endtrans %}</p>
<h3>{% trans %}What is included:{%- endtrans %}</h3>
<p>{% trans %}<strong>The Set Up Wizard</strong>: When you download the
I2P software, a set up wizard will guide you through a few configuration steps
@@ -18,8 +16,8 @@ while your router is making its first connections to the network. This happens
the same way that your home router connects you to the Internet. During the set
up process, you will be given the option to test your bandwidth and set your
bandwidth limits in order to ensure a good connection as a network peer.{%- endtrans %}</p>
-<p>{% trans %}<strong>The I2P Router Console</strong>: Here is where you can see your
-network connections and information about your router. You will be able to see how many peers you
+<p>{% trans %}<strong>The I2P Router Console</strong>: Here is where you can see your router
+network connections. You will be able to see how many peers you
have, and other information that will help if you need to troubleshoot. You can
stop and start the router as well. You will see the applications that the
software includes, as well as links to some community forums and sites on the
@@ -47,7 +45,7 @@ a camera. This is especially useful for Android devices.</p>
adapter for forwarding services ( ie SSH ) into I2P and proxying client
requests to and from I2P. It provides a variety of “Tunnel Types†which are
able to do advance filtering of traffic before it reaches I2P.{%- endtrans %}</p>
-<h3>{% trans %}Applications Outside I2P to use with I2P{%- endtrans %}</h3>
+<h3>{% trans %}I2P Network Compatible Applications{%- endtrans %}</h3>
<p>{% trans browser=site_url('about/browser-config') %}<strong><a href="{{ browser }}">Mozilla Firefox</a></strong>: A web browser with advanced privacy and
security features, this is the best browser to configure to browse I2P
sites.{%- endtrans %}</p>
diff --git a/i2p2www/pages/site/contact.html b/i2p2www/pages/site/contact.html
index 6a17e0a2bfb4d0fce543584a47cca23243193d30..97c150fd2855baef504d014dc80b1ba44c1374db 100644
--- a/i2p2www/pages/site/contact.html
+++ b/i2p2www/pages/site/contact.html
@@ -82,19 +82,14 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<table border="0">
<tr>
<td valign="top" rowspan="31"><b>{{ _('Admin') }}</b></td>
- <td valign="top"><b>{{ _('Project Manager') }}</b></td>
+ <td valign="top"><b>{{ _('I2P Java Release Manager') }}</b></td>
<td valign="top">idk</td>
- <td valign="top"><i>{{ _('point of contact of last resort') }}</i></td>
-</tr>
-<tr>
- <td valign="top"><b>{{ _('Donations treasurer') }}</b></td>
- <td valign="top"></td>
- <td valign="top"><i>{{ _('manage donations') }}</i></td>
+ <td valign="top"><i>{{ _('Builds and signs the releases') }}</i></td>
</tr>
<tr>
- <td valign="top"><b>{{ _('PR manager') }}</b></td>
+ <td valign="top"><b>{{ _('Outreach') }}</b></td>
<td valign="top">Sadie</td>
- <td valign="top"><i>{{ _('press contact, manages public relations and affairs') }}</i></td>
+ <td valign="top"><i>{{ _('Coordinator with community, NGOs and human rights groups. Meeting facilitator, Digital Security training and Press') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{{ _('Assistant PR manager') }}</b></td>
@@ -104,7 +99,7 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<tr>
<td valign="top"><b>{% trans forum=i2pconv('i2pforum.i2p') %}<a href="http://{{ forum }}/">Forum</a> admin{% endtrans %}</b></td>
<td valign="top">eche|on</td>
- <td valign="top"><i>{{ _('manage the public user forum') }}</i></td>
+ <td valign="top"><i>{{ _('I2P public forum maintainer') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{{ _('Download mirrors admin') }}</b></td>
@@ -136,55 +131,45 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<td valign="top">echelon</td>
<td valign="top"><i>{{ _('OSX installer packager') }}</i></td>
</tr>
-<tr>
- <td valign="top"><b>{{ _('Release Manager') }}</b></td>
- <td valign="top">idk</td>
- <td valign="top"><i>{{ _('Builds and signs the releases') }}</i></td>
-</tr>
<tr>
<td valign="top"><b>{{ _('Release Manager Alternates') }}</b></td>
- <td valign="top">eche|on, str4d</td>
+ <td valign="top">eche|on</td>
<td valign="top"><i>{{ _('Backup release managers') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{{ _('CI admin') }}</b></td>
<td valign="top">idk</td>
- <td valign="top"><i>{{ _('Maintain the Continuous Integration infrastructure') }}</i></td>
+ <td valign="top"><i>{{ _('Maintain Continuous Integration infrastructure') }}</i></td>
</tr>
<tr>
- <td valign="top"><b>{{ _('Reseed admin') }}</b></td>
+ <td valign="top"><b>{{ _('Reseed Admin') }}</b></td>
<td valign="top">backup</td>
<td valign="top"><i>{{ _('Monitors, advises and recruits reseed hosts') }}</i></td>
</tr>
-<tr>
- <td valign="top"><b>{{ _('Security Researcher') }}</b></td>
- <td valign="top" class="blue">[{{ _('vacant') }}]</td>
- <td valign="top"><i>{{ _('threat model / crypto expert') }}</i></td>
-</tr>
<tr>
<td valign="top"><b><a href="https://i2pgit.org/">Gitlab</a> admin</b></td>
<td valign="top">idk</td>
- <td valign="top"><i>{{ _('Manage the project gitlab') }}</i></td>
+ <td valign="top"><i>{{ _('I2P Gitlab maintainer') }}</i></td>
</tr>
<tr>
- <td valign="top"><b><a href="https://i2pgit.org/dashboard/issues">Issue Tracker(Replaces Trac)</a> admin</b></td>
- <td valign="top">idk</td>
- <td valign="top"><i>{{ _('Manage the project bug tracker') }}</i></td>
-</tr>
-<tr>
- <td valign="top"><b>{{ _('Translation admins') }}</b></td>
+ <td valign="top"><b>{{ _('Localization') }}</b></td>
<td valign="top">eche|on, idk, Sadie</td>
<td valign="top">Admins on <a href="https://www.transifex.com/projects/p/I2P/">Transifex</a></td>
</tr>
<tr>
- <td valign="top"><b>{{ _('User Advocate') }}</b></td>
+ <td valign="top"><b>{{ _('Translators') }}</b></td>
+ <td valign="top">{{ _('many many people!') }}</td>
+ <td valign="top">Translators on <a href="https://www.transifex.com/projects/p/I2P/">Transifex</a></td>
+</tr>
+<tr>
+ <td valign="top"><b>{{ _('Usability Lead') }}</b></td>
<td valign="top">Sadie</td>
- <td valign="top"><i>{{ _('gather, prioritize, advocate for user needs') }}</i></td>
+ <td valign="top"><i>{{ _('Usability research') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{{ _('Product Development') }}</b></td>
<td valign="top">Sadie</td>
- <td valign="top"><i>{{ _('supervises projects from the early planning stages to project completion') }}</i></td>
+ <td valign="top"><i>{{ _('supervises projects from the early planning stages to project completion') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{{ _('Website Maintainer') }}</b></td>
@@ -194,12 +179,12 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<tr>
<td valign="top"><b>{% trans website=site_url() %}<a href="{{ website }}">Webserver</a> admin{% endtrans %}</b></td>
<td valign="top">eche|on</td>
- <td valign="top"><i>{{ _('manage the public project webservers') }}</i></td>
+ <td valign="top"><i>{{ _('manage public project webservers') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{% trans website=site_url() %}<a href="{{ website }}">Website</a> admin{% endtrans %}</b></td>
<td valign="top">idk</td>
- <td valign="top"><i>{{ _('manage the public project website content') }}</i></td>
+ <td valign="top"><i>{{ _('manage the public project website') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{{ _('News Admin') }}</b></td>
@@ -211,11 +196,6 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<td valign="top">idk</td>
<td valign="top"><i>{{ _('manage the backup news feed') }}</i></td>
</tr>
-<tr>
- <td valign="top"><b>{{ _('Design and Usability') }}</b></td>
- <td valign="top">Sadie, idk</td>
- <td valign="top"><i>{{ _('ongoing improvements to user experience for website and software') }}</i></td>
-</tr>
<tr>
<td valign="top"><b>Google Play admin</b></td>
<td valign="top">idk</td>
@@ -231,28 +211,14 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<td valign="top">StormyCloud</td>
<td valign="top"><i></i></td>
</tr>
+</table>
+<table>
<tr>
- <!--<td valign="top"><b>{{ _('Director of passion') }}</b></td>
- <td valign="top" class="blue">[{{ _('vacant') }}]</td>
- <td valign="top"><i>{{ _('community motivator') }}</i></td>-->
-</tr>
-<tr><td colspan="4"><hr /></td></tr>
-<tr>
- <td valign="top" rowspan="17"><b>{{ _('Dev') }}</b></td>
- <td valign="top"><b>{{ _('Core Lead') }}</b></td>
- <td valign="top">idk</td>
- <td valign="top"><i>{{ _('lead dev for the SDK and router') }}</i></td>
-</tr>
-<tr>
+ <td valign="top" rowspan="17"><b>{{ _('I2P Core Integration Mainatainers') }}</b></td>
<td valign="top"><b>{% trans postman=i2pconv('hq.postman.i2p') %}<a href="http://{{ postman }}/">I2P mail</a> lead{% endtrans %}</b></td>
<td valign="top">postman</td>
<td valign="top"><i>{{ _('organize and develop the i2p mail system') }}</i></td>
</tr>
-<tr>
- <td valign="top"><b>{% trans bote=i2pconv('bote.i2p') %}<a href="http://{{ bote }}/">I2P-Bote</a> lead{% endtrans %}</b></td>
- <td valign="top">str4d</td>
- <td valign="top"><i>{{ _('I2P-Bote plugin') }}</i></td>
-</tr>
<tr>
<td valign="top"><b>{% trans forum=i2pconv('i2pforum.i2p') %}<a href="http://{{ forum }}/viewforum.php?f=12">I2PSnark</a> lead{% endtrans %}</b></td>
<td valign="top">idk</td>
@@ -283,11 +249,6 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<td valign="top">idk</td>
<td valign="top"><i>{{ _('SAM maintainer') }}</i></td>
</tr>
-<tr>
- <td valign="top"><b>{{ _('Translators') }}</b></td>
- <td valign="top">{{ _('many many people!') }}</td>
- <td valign="top">Translators on <a href="https://www.transifex.com/projects/p/I2P/">Transifex</a></td>
-</tr>
<tr>
<tr>
<td valign="top" rowspan="6"><b>{{ _('Contributors') }}</b></td>
@@ -311,7 +272,8 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
<td valign="top" class="blue"><i>{{ _('Help needed on many fronts!') }}</i></td>
</tr>
-<tr><td colspan="4"><hr /></td></tr>
+</table>
+<table>
<tr>
<td valign="top" rowspan="39" colspan="2"><b>{{ _('Past contributors') }}</b></td>
<td valign="top">mihi</td>
@@ -472,7 +434,7 @@ GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B F47E CFCD C461 75E6 694A</tt>
<td valign="top" colspan="2">{% trans %}… and many others{% endtrans %}</td>
</tr>
<tr>
- <td><a href="site_url(about/hall-of-fame)">Hall of Fame!</a></td>
+ <td>{% trans website=site_url(about/hall-of-fame) %}<a href="{{ website }}">Hall of Fame!</a></td>
</tr>
</table>
diff --git a/i2p2www/pages/site/docs/plugins.html b/i2p2www/pages/site/docs/plugins.html
index d2519f98d778b56c0346ebc785122c31a23008d1..8f2719047a4e0e7c09df84dbcc5e42cf1e3c4394 100644
--- a/i2p2www/pages/site/docs/plugins.html
+++ b/i2p2www/pages/site/docs/plugins.html
@@ -5,8 +5,8 @@
{% block content %}
<h2>{% trans %}General Information{% endtrans %}</h2>
<p>{% trans -%}
-I2P includes a plugin architecture
-to support easy development and installation of additional software.
+The I2P network includes a plugin architecture
+to support both easy development and installation of new plugins.
{%- endtrans %}</p>
<p>{% trans -%}
@@ -14,7 +14,7 @@ There are now plugins available that support distributed email, blogs, IRC
clients, distributed file storage, wikis, and more.
{%- endtrans %}</p>
-<h3>{% trans -%}Easy Installation of Applications{%- endtrans %}</h3>
+<h3>{% trans -%}Adding Plugins To Your I2P Router{%- endtrans %}</h3>
<p>{% trans -%}
I2P Plugins can be installed by copying the plugin download URL onto
the appropriate section on the <a href="http://127.0.0.1:7657/configplugins">Router Console Plugin Configuration Page</a>.
@@ -131,8 +131,7 @@ builds).
<h3>{% trans %}Development{% endtrans %}</h3>
<p>{% trans pluginspec=site_url('docs/spec/plugin'), zzz=i2pconv('zzz.i2p') -%}
-See the latest <a href="{{ pluginspec }}">plugin specification</a> and the
-<a href="http://{{ zzz }}/forums/16">plugin forum</a> on {{ zzz }}.
+See the latest <a href="{{ pluginspec }}">plugin specification</a>
{%- endtrans %}</p>
<p>{% trans pluginsite=i2pconv('plugins.i2p') -%}
@@ -141,10 +140,6 @@ as <a href="http://{{ pluginsite }}/plugins/snowman">snowman</a>, were developed
specifically as examples.
{%- endtrans %}</p>
-<p>{% trans -%}
-<b>Developers wanted!</b> Plugins are a great way to learn more about I2P
-or easily add some feature.
-{%- endtrans %}</p>
<h3>{% trans %}Getting Started{% endtrans %}</h3>
<p>{% trans url='https://github.com/i2p/i2p.scripts/tree/master/plugin/makeplugin.sh' -%}
diff --git a/i2p2www/pages/site/docs/reseed.html b/i2p2www/pages/site/docs/reseed.html
index f04b59590e6c4bb14a354d38677d4d0b422bee1d..adc113b61e83bf56eecd0be6c8cb2e9b69d73eda 100644
--- a/i2p2www/pages/site/docs/reseed.html
+++ b/i2p2www/pages/site/docs/reseed.html
@@ -5,29 +5,28 @@
{% block content %}
-<h2 id="about">{% trans %}About Reseed hosts{% endtrans %}</h2>
+<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 for new routers to integrate with the I2P network.
+During the bootstrapping process, reseed hosts provide an initial set of nodes for
+a new router to make connections with. Occasionally an already integrated router
+may need to go through the reseed process if it is experiencing connection issues with the network.
+This is most often caused by its known nodes not being available.
{%- 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.
+information is signed by the reseed host you connect to. This makes it impossible
+for an unauthenticated source to provide false information.
{%- endtrans %}</p>
<h2 id="running">{% trans %}Running a Reseed host{% endtrans %}</h2>
<p>
-{% 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.
+{% trans -%}Operating a reseed server will be familair for most sysadmins who have experience with
+I2P. More reseed hosts result in more resilient I2P network connections for new
+participating routers. It also makes it harder to prevent new routers from connecting to the I2P network.
{%- endtrans %}
</p>
@@ -36,29 +35,27 @@ prevent users of I2P from connecting to the network.
<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>
+<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
+Other options for reseeding include file-based reseeds, 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.
+to them as a .zip file. Using cloud-based infrastructure helps to resist
+censorship, which aids people in situations where reseeds may be 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-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>
+<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
+If you are running a reseed server, thank you for helping to
make the I2P network stronger and more resilient than ever.
{%- endtrans-%}
</p>
diff --git a/i2p2www/pages/site/faq.html b/i2p2www/pages/site/faq.html
index 566e277c41521a96138a99f80ab260f0b621cf92..151b6b785259bcbc05e8cfc65d010603ab552f12 100644
--- a/i2p2www/pages/site/faq.html
+++ b/i2p2www/pages/site/faq.html
@@ -116,37 +116,30 @@ Try hovering your cursor over the other lines of information for a brief descrip
<h3 id="badcontent"><span class="permalink"><a href="#badcontent">
{% trans %}I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?{% endtrans %}</a></span>
</h3>
-<p>{% trans -%}
-I2P is an anonymous network - it is designed to withstand attempts at blocking or censoring of content, thus providing a means for communication that anyone can use.
+<p>{% trans -%}
I2P traffic that transits through your router is encrypted with several layers of encryption.
Except in the case of a serious security vulnerability (of which none are currently known),
-it is not possible to know what the contents of the traffic are and thus not possible to distinguish between traffic which one is opposed to or not opposed to.
-
- We consider the 3 parts of the question:
+it is not possible to know the content, origin or destination of routed traffic.
{%- endtrans %}</p>
<ul>
<li>
{% trans -%}
<b>Distribution</b><br>
-All traffic on I2P is encrypted in multiple layers. You don't know a message's contents, source, or destination.
-All traffic you route is internal to the I2P network, you are not an <a href="#exit">exit node</a> (referred to as an outproxy in our documentation).
-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.
+All traffic on the I2P network is encrypted in multiple layers. You don't know a message's contents, source, or destination.
+Traffic is internal to the I2P network, you are not an <a href="#exit">exit node</a> (referred to as an outproxy in our documentation).
{%- endtrans %}
</li>
<li>
{% trans -%}
<b>Storage</b><br>
-I2P does not do distributed storage of content, this has to be specifically installed and configured by the user (with Tahoe-LAFS, for example).
+The I2P network does not do distributed storage of content, this has to be specifically installed and configured by the user (with Tahoe-LAFS, for example).
That is a feature of a different anonymous network, <a href="http://freenetproject.org/">Freenet</a>.
-By running I2P, you are not storing content for anyone.
+By running an I2P router, you are not storing content for anyone.
{%- endtrans %}
</li>
<li>
{% trans -%}
<b>Access</b><br>
-If there are hidden services which you dislike, you may refrain from visiting them.
Your router will not request any content without your specific instruction to do so.{%- endtrans %}
</li>
</ul>
diff --git a/i2p2www/pages/site/get-involved/index.html b/i2p2www/pages/site/get-involved/index.html
index 081347d326b56a9646b2689d3ba928e08faae36b..d08659e85882e617b1bfb1de4a971d7d518294c0 100644
--- a/i2p2www/pages/site/get-involved/index.html
+++ b/i2p2www/pages/site/get-involved/index.html
@@ -1,15 +1,13 @@
{% extends "global/layout.html" %} {% block title %}{% trans %}Get Involved{% endtrans %}{% endblock %} {% block content %}
-<h2>{% trans %}There are many ways you can help I2P.{% endtrans %}</h2>
-<h3>{% trans %}Grow the Community{% endtrans %}</h3>
+<h2>{% trans %}Contribute to the I2P Network .{% endtrans %}</h2>
+
<ul>
+ </li>
<li><b>{% trans %}Support I2P Core Development{% endtrans %}</b>{% trans %}The project hosts meetings on the first Tuesday of every month that are open to the community. This is a great opportunity to see what is happening with I2P core development and
- familiarize yourself with Roadmap tasks. Additionally, protocol development meetings take place every Tuesday and zzz's development forum is available all of the time as a place to participate in development and issues that need fixing. See the
+ familiarize yourself with Roadmap tasks. See the
new developer's guide for how to get started.{% endtrans %}
</li>
- <li><b>{% trans %}Spread the Word.{% endtrans %}</b> — {% trans -%} Tell people about I2P on forums, blogs, and comments to articles. Fix up the
- <a href="https://wikipedia.org/wiki/I2P">Wikipedia article about I2P in your language</a>. Tell your friends, and more importantly, use I2P to communicate with your friends. We have many tools that can help you keep your private conversations
- private. {%- endtrans %}
- </li>
+
<li><b><a href="{{ newtrans }}">{{ _('Translation and Documentation') }}</a></b> — {% trans newtrans=site_url('get-involved/guides/new-translators') -%} Help translate the website and the software into your language. Translators are a very important
part of this decentralized project and your work is always appreciated. See the new translator's guide for details. The project also welcomes support to help keep its documentation updated. See the <a href="{{ newtrans }}">new translator's guide</a> for details. {%- endtrans %}
</li>
@@ -17,10 +15,10 @@
<h3>{% trans %}Host Services for Yourself and Others{% endtrans %}</h3>
<ul>
<li><b><a href="{{ site_url('/about/software') }}">{{ _('Services') }}</a></b> — {% trans -%} Self-hosting almost anything, from an SSH server for yourself to an ActivityPub forum for everyone and anything in between, is helpful to the I2P network,
- especially if you write down instructions for others. Almost anything you can think of can be made to work with I2P, and your service is valuable to the network. {%- endtrans %}
+ especially if you write down instructions for others. Almost anything you can think of can be made to work with I2P. {%- endtrans %}
</li>
- <li><b><a href="{{ reseed }}">{{ _('Reseeding') }}</a></b> — {% trans reseed=site_url('get-involved/guides/reseed') -%} Getting new users onto the network is a very important task, and that task is handled by our reseed servers. The more reseed
- servers we have, the more de-centralized and redundant our infrastructure is. It's a big responsibility, but it's pretty easy to set up a reseed server for new routers to bootstrap from. Detailed instructions are on our <a href="{{ reseed }}">reseed server page</a>.
+ <li><b><a href="{{ reseed }}">{{ _('Reseeding') }}</a></b> — {% trans reseed=site_url('get-involved/guides/reseed') -%} Getting new participanting routers onto the network is a very important task, and that task is handled by reseed servers. The more reseed
+ servers the network has, the more de-centralized and redundant its infrastructure becomes. It's a big responsibility, but it's pretty easy to set up a reseed server for new routers to bootstrap from. Detailed instructions can be found here <a href="{{ reseed }}">reseed server page</a>.
{%- endtrans %}
</li>
</ul>
@@ -29,18 +27,16 @@
<li><b><a href="{{ site_url('/get-involved/guides/dev-guidelines') }}">{{ _('Applications') }}</a></b> — {% trans apps=site_url('get-involved/develop/applications') -%} Write or port applications for I2P. There's some guidelines and a list of ideas
on the <a href="{{ apps }}">applications page</a>. {%- endtrans %}
</li>
- <li><a href="{{ site_url('/get-involved/guides/new-developers') }}"><b>{{ _('Coding') }}</a></b> — {% trans trac=i2pconv('trac.i2p2.i2p'), zzz=i2pconv('zzz.i2p'), newdevs=site_url('get-involved/guides/new-developers') -%} There's plenty to do if
- you know Java or are ready to learn. Check for open tickets on <a href="http://{{ trac }}/report/1">Trac</a> or the TODO list on <a href="http://{{ zzz }}">{{ zzz }}</a> for some ideas on where to start. See the <a href="{{ newdevs }}">new developer's guide</a> for details. {%- endtrans %}
- </li>
- <li><b><a href="{{ site_url('research/index') }}">{{ _('Analysis') }}</b> — {% trans threatmodel=site_url('docs/how/threat-model') -%} Study or test the code to look for vulnerabilities. Both anonymity vulnerabilities from the various
+
+ <li><b><a href="{{ site_url('research/index') }}">{{ _('Research') }}</b> — {% trans threatmodel=site_url('docs/how/threat-model') -%} Study or test I2P code to look for vulnerabilities. Both anonymity vulnerabilities from the various
<a href="{{ threatmodel }}">threat models</a>, and DOS and other weaknesses due to security holes, benefit from ongoing research. {%- endtrans %}
</li>
</ul>
-<h4>{% trans %}When you're ready, join us on our Gitlab{% endtrans %}</h4>
+<h4>{% trans %}Join I2P On Gitlab{% endtrans %}</h4>
<ul>
<li><strong><a href="http://git.idk.i2p">{% trans %}Inside I2P - (http://git.idk.i2p){% endtrans %}</a></strong>
</li>
<li><strong><a href="https://i2pgit.org">{% trans %}Outside I2P - (https://i2pgit.org){% endtrans %}</a></strong>
</li>
</ul>
-{% endblock %}
\ No newline at end of file
+{% endblock %}
diff --git a/i2p2www/pages/site/research/index.html b/i2p2www/pages/site/research/index.html
index 3200430492421324caceb5e7cad4cf9a912d920f..f93800fdc3c2ba4cc01b70fb8d850ea0a9f7673d 100644
--- a/i2p2www/pages/site/research/index.html
+++ b/i2p2www/pages/site/research/index.html
@@ -8,11 +8,8 @@
<h3>{{ _('Research on the I2P Network') }}</h3>
<p>{% trans -%}
-I2P is a very unique project that unfortunately has not received the wider
-academic attention it deserves. To date, most research focus on anonymous and
-onion-routing technology has been around Tor, and while those papers benefit us
-as well, there is a great need for I2P-focused research. This plays a key role
-in both maintaining the security and integrity of the network, as well as
+Research plays a key role
+in both maintaining the security and integrity of the I2P network, as well as
opening doors for more impactful future development.
{%- endtrans %}</p>
@@ -32,9 +29,9 @@ A list of known published papers about I2P is available <a href="{{ papers
{%- endtrans %}</p>
<p>{% trans %}
-This page aims to outline the most needed fields of research, notes to
-potential researchers, our general safety guidelines as well as an expanding
-list of open questions that you can begin on at any time.
+This page outlines the most needed fields of research, notes to
+potential researchers, general safety guidelines as well as an expanding
+list of open research questions.
{% endtrans %}</p>
<h2>{{ _('Notes to Researchers:') }}</h2>
@@ -43,12 +40,9 @@ list of open questions that you can begin on at any time.
<p>{% trans -%}
While all research on the I2P network is beneficial and appreciated, there are
-certain areas which are more in need than others - most so in defensive
-research. Most people enjoy coming up with fun ways to launch offensives
+certain areas that are more in need than others. Most research focuses on testing offensives
against anonymous software, and this is further reinforced by the incentives in
-academic institutions. While we know it is often not the first choice for
-researchers, We would certainly appreciate any and all work towards ways to
-fortify the network!
+academic institutions. The project would appreciate research and testing that will support fortifying the I2P network.
{%- endtrans %}</p>
<h3>{{ _('Offensive and Analytic Tests') }}</h3>
diff --git a/i2p2www/pages/site/research/vrp.html b/i2p2www/pages/site/research/vrp.html
index 43b35b90626438b4697391291326925ca2571fb0..173e44a2a21d21c02e799e8bad0df9eb2c61a5fd 100644
--- a/i2p2www/pages/site/research/vrp.html
+++ b/i2p2www/pages/site/research/vrp.html
@@ -7,13 +7,13 @@
This process is subject to change. Please refer to this page for the current VRP.
{%- endtrans %}</p>
-<p>{% trans %}This page was last updated in June 2020.{%- endtrans %}</p>
+<p>{% trans %}This page was last updated April 2023.{%- endtrans %}</p>
-<p>{% trans %}Researchers: while you research/hack, we ask that you refrain from the following: - Performing active exploits or Denial of Service attacks on the
-i2p network - Performing social engineering on i2p development team members - Performing any physical or electronic attempts against i2p property and/or data
+<p>{% trans %}Researchers: during your study and network testing, we ask that you refrain from the following: - Performing active exploits or Denial of Service attacks on the
+I2P network - Performing social engineering on I2P team and community members - Performing any physical or electronic attempts against I2P property and/or data
centers{%- endtrans %}</p>
-<p>{% trans %}As i2p is an open-source community, many volunteers and development team members run their own I2P Sites as well as public (“non-private internetâ€) domains. These
-sites/servers are NOT in the scope of the vulnerability assessment / response process, only the underlying code of i2p is.{%- endtrans %}</p>
+<p>{% trans %}As I2P is an open-source community, many volunteers and development team members run their own I2P Sites as well as public (“non-private internetâ€) domains. These
+sites/servers are NOT in the scope of the vulnerability assessment / response process, only the underlying code of I2P is.{%- endtrans %}</p>
<h2 id="i.-point-of-contact-for-security-issues">I. {{ _('Point of Contact for Security Issues') }}</h2>
@@ -22,7 +22,7 @@ sites/servers are NOT in the scope of the vulnerability assessment / response pr
<h2 id="ii.-security-response-team">II. {{ _('Security Response Team') }}</h2>
<p>{% trans -%}
-Echelon is the trusted security point-of-contact. He forwards e-mails to team members as appropriate.
+Echelon is the trusted security point-of-contact. He forwards emails to team members as appropriate.
{%- endtrans %}</p>
<h2 id="iii.-incident-response">III. {{ _('Incident Response') }}</h2>