I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Update faq.html

Browse Source
This commit is contained in:
Sadie Mascis
2023-04-17 11:53:19 -04:00
committed by GitHub
parent 37442a469e
commit 173790ed7c
1 changed files with 6 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
i2p2www/pages/site/faq.html
View File

@ -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&#37; 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>