Replace all references to eepSite with I2P Site

This commit is contained in:
idk
2020-11-27 16:16:49 -05:00
parent 1a39ae4cab
commit bc139e5a7c
54 changed files with 116 additions and 116 deletions

View File

@ -100,7 +100,7 @@ usually a secret. What is hidden is information on what the user is doing,
if anything at all, as well as what router a particular destination is connected
to. End users will typically have several local destinations on their router
- for instance, one proxying in to IRC servers, another supporting the user's
anonymous webserver ("I2P site"), another for an I2Phex instance, another for
anonymous webserver ("I2P Site"), another for an I2Phex instance, another for
torrents, etc.
{%- endtrans %}</p>
@ -904,7 +904,7 @@ system. It lets you create information, share it with others, and read posts
from those you're interested in, all while taking into consideration your
needs for security and anonymity. Rather than building its own content distribution
network, Syndie is designed to run on top of existing networks, syndicating
content through I2P sites, Tor hidden services, Freenet freesites, normal websites,
content through I2P Sites, Tor hidden services, Freenet freesites, normal websites,
usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie
is done so as to offer pseudonymous authentication to anyone reading or archiving
it.
@ -945,7 +945,7 @@ be sufficient for some users.
<p>{% trans -%}
I2PTunnel enables most of the applications in use. An "httpserver" pointing
at a webserver lets anyone run their own anonymous website (or "I2P site")
at a webserver lets anyone run their own anonymous website (or "I2P Site")
- a webserver is bundled with I2P for this purpose, but any webserver can
be used. Anyone may run a "client" pointing at one of the anonymously hosted
IRC servers, each of which are running a "server" pointing at their local
@ -963,7 +963,7 @@ proxies to access the "server" instances pointing at an NNTP server.
<p>{% trans -%}
i2p-bt is a port of the mainline python BitTorrent client to run both the
tracker and peer communication over I2P. Tracker requests are forwarded through
the eepproxy to I2P sites specified in the torrent file while tracker responses
the eepproxy to I2P Sites specified in the torrent file while tracker responses
refer to peers by their destination explicitly, allowing i2p-bt to open up
a <a href="#app.streaming">streaming lib</a> connection to query them for
blocks.
@ -1041,7 +1041,7 @@ SMTP and POP3 servers - both the outproxies and inproxies communicate with
the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those
non-anonymous locations does not give access to the mail accounts or activity
patterns of the user. At the moment the developers work on a decentralized
mailsystem, called "v2mail". More information can be found on the I2P site
mailsystem, called "v2mail". More information can be found on the I2P Site
<a href="http://{{ postman }}/">{{ postman }}</a>.
{%- endtrans %}</p>