forked from I2P_Developers/i2p.www
FAQ, Footer, and Index text finalization
This commit is contained in:
@@ -673,14 +673,14 @@ There is an <a href="{{ outproxy }}">outproxy guide</a> available on our forums,
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h3 id="safe"><span class="permalink"><a href="#safe">{% trans %}Is using I2P Safe?{% endtrans %}</a></span></h3>
|
||||
<p>{% trans %}I2P strives to be safe in it's default configuration for all users. In most, possibly all countries, anonymizing
|
||||
software and strong encryption are not illegal to possess or use.{% endtrans %}</p>
|
||||
|
||||
<p>{% trans %} It may be dangerous to use I2P in what the project calls "Strict Countries" where the law may not be clear on anonymizing software and where risks are judged to be fairly high. Most I2P peers are not in those strict countries and the ones that are are placed in "Hidden Mode" where they interact with the rest of the network in more limited ways, so that they are less visible to network observers. Structurally, taking over a single peer, or even a fairly large group of peers, with a subpoena is not an effective way to deanonymizing anybody else's traffic.
|
||||
{% endtrans %}</p>
|
||||
|
||||
<p>Before you use I2P, use Basic Computer Hygiene Always! Apply your OS vendor provided software updates in a prompt manner. Be aware of the state of your firewall and anti-virus status if you use one. Always get your software from authentic sources.</p>
|
||||
|
||||
<p>{% trans %}I2P strives to be safe in it's default configuration for all users.{% endtrans %}</p>
|
||||
|
||||
<p>{% trans %} It may be dangerous to use I2P in what the project calls "Strict Countries" where the law may not be clear on anonymizing software and where risks are judged to be fairly high. Most I2P peers are not in those strict countries and the ones that are, are placed in "Hidden Mode" where they interact with the rest of the network in more limited ways, so that they are less visible to network observers.
|
||||
{% endtrans %}</p>
|
||||
|
||||
<h3 id="netdb_ip"><span class="permalink"><a href="#netdb_ip">
|
||||
{% trans %}I see IP addresses of all other I2P nodes in the router console. Does that mean my IP address is visible by others?{% endtrans %}</a></span>
|
||||
</h3>
|
||||
|
@@ -5,7 +5,7 @@
|
||||
{% block content_outer %}
|
||||
<div class="main">
|
||||
<!--<img src="{{ url_for('static', filename='images/pexels-jakub-novacek.jpg') }}" class="home_splash_image" />-->
|
||||
<h1>{{ _('What does I2P do for you?') }}</h1>
|
||||
<h1>{{ _('Welcome to the Invisible Internet') }}</h1>
|
||||
<p>{% trans %}The Invisible Internet is a privacy by design, people-powered network. It is a truly free and anonymizing Internet alternative. Get I2P.
|
||||
{% endtrans %}</p>
|
||||
<a class="get-i2p" href="{{ url_for('downloads_list', lang=g.lang) }}">{% trans version=ver() %}Get I2P {{ version }}{% endtrans %}</a>
|
||||
@@ -19,44 +19,30 @@
|
||||
activity, location and your identity. The software ships with a router that connects you to the
|
||||
network and applications for sharing, communicating and building. {%- endtrans %}</li>
|
||||
</ul>
|
||||
<h1>{% trans %}I2P Cares about Privacy{% endtrans %}</h1>
|
||||
<h1>{% trans %}I2P Cares About Privacy{% endtrans %}</h1>
|
||||
<ul>
|
||||
<li>{% trans %}The Invisible Internet values privacy and consent. It is about your choice to share,
|
||||
your platform to own, and the connections you want to make. It is privacy by design, plain, simple
|
||||
and truly free. Additionally I2P offers resistance to analysis and blocking by censors.{%- endtrans %}</li>
|
||||
<li>{% trans %}I2P hides the server from the user and the user from the server. All I2P traffic is
|
||||
internal to the I2P network. It does not connect you with the internet, but it is a layer on top of
|
||||
the Internet. It uses encrypted, nested tunnels between you and your peers to assure that no one can
|
||||
see where traffic is coming from, where it is going or what the contents are. {%- endtrans %}
|
||||
</li>
|
||||
<li>{% trans %}I2P hides the server from the user and the user from the server. All I2P traffic is internal to the I2P network. Traffic inside I2P does not interact with the Internet directly. It is a layer on top of the Internet. It uses encrypted unidirectional tunnels between you and your peers. No one can see where traffic is coming from, where it is going, or what the contents are. Additionally I2P offers resistance to pattern recognition and blocking by censors. Because the network relies on peers to route traffic, location blocking is also reduced.{%- endtrans %}</li>
|
||||
<li>
|
||||
<a href="{{ site_url('about/intro') }}"><em>{% trans %}Read more…{% endtrans %}</em></a>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="aside">
|
||||
<h1>Peer-to-Peer</h1>
|
||||
<p>Everyday, people use the I2P network to connect with other people without the worry of being tracked or their data being collected. In some cases people rely on the network when they cannot safely communicate or while doing sensitive work. The network is P2P - people powered, and always growing. <a href="https://geti2p.net/en/docs/protocol">Learn more about the Protocol Stack</a>.</p>
|
||||
|
||||
<h1>Privacy and Security By Design</h1>
|
||||
<p>I2P has created transport protocols that resist DPI censorship, and continuously improves its end to end encryption.
|
||||
<a href="https://geti2p.net/en/docs/transport">Read the I2P Transport Overview</a></p>
|
||||
|
||||
<h1>Built For Communication</h1>
|
||||
<p>I2P has an application layer with easy to use <a href="https://geti2p.net/en/docs/api/i2ptunnel">API’s for creating your own privacy - aware apps.</a></p>
|
||||
</div>
|
||||
<div class="aside">
|
||||
<a href="{{ url_for('blog_atom', lang=g.lang) }}" class="feed-icon" title="{{ _('I2P Blog ATOM Feed') }}">{{ _('I2P Blog ATOM Feed') }}</a>
|
||||
<h1>{% trans %}News & Updates{% endtrans %}</h1>
|
||||
{% include "blog/latest.html" %}
|
||||
</div>
|
||||
<div class="aside">
|
||||
<h1>{% trans %}Conferences Calendar 2020{% endtrans %}</h1>
|
||||
<p>I2P Developers will be visiting these conferences this year:</p>
|
||||
<p><b>Upcoming:</b></p>
|
||||
<ul>
|
||||
<li>Conference attendance is limited at this time due to COVID-19, and
|
||||
many conferences have been postponed or canceled. This section will
|
||||
be updated when the situation becomes clearer.</li>
|
||||
</ul>
|
||||
<p><b>Past:</b></p>
|
||||
<ul>
|
||||
<li>Chaos Communications Congress (December 27-30 2019, Leipzig, Germany)</li>
|
||||
<li>Our Networks Conference (September 20-22 2019, Toronto, Canada)</li>
|
||||
<li>DEF CON 27 (August 8-11 2019, Las Vegas, Nevada)</li>
|
||||
<li>USENIX FOCI (August 13, 2019, Santa Clara, California)</li>
|
||||
<li>Internet Freedom Festival (April 1-5 2019, Valencia, Spain)</li>
|
||||
<li>RightsCon (June 11-14 2019, Tunis, Tunisia)</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
Reference in New Issue
Block a user