kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace all references to eepSite with I2P Site

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files

2
i2p2www/pages/downloads/debian.html
View File

@@ -238,7 +238,7 @@ as the default settings of 96 KB/s down / 40 KB/s up are fairly conservative.
{%- endtrans %}</p>
<p>{% trans browserconfig=site_url('about/browser-config') -%}
If you want to reach I2P sites via your browser, have a look on the <a href="{{ browserconfig }}">browser proxy setup</a> page for an easy howto.
If you want to reach I2P Sites via your browser, have a look on the <a href="{{ browserconfig }}">browser proxy setup</a> page for an easy howto.
{%- endtrans %}</p>
{% endblock %}

2
i2p2www/pages/downloads/firefox.html
View File

@@ -4,7 +4,7 @@
{% block content %}
<h1>{{ _('I2P Firefox Browser Profile') }}</h1>
<p>{% trans -%}
Now that you have joined the I2P network, you will want to see I2P sites and and
Now that you have joined the I2P network, you will want to see I2P Sites and and
other content that is hosted on the network. The Firefox browser is
pre-configured to allow you to access the content available on the network. It
also keeps your I2P search activity separate from your internet search activity.

2
i2p2www/pages/downloads/list.html
View File

@@ -65,7 +65,7 @@ Windows: Java 8 is recommended. Java 9 or higher may not work.
<p>
When you download the I2P software bundle, you get everything you need to connect
and start participating in the I2P network and community. It even includes basic
applications for every user, like e-mail, bittorrent, and a basic I2P site for
applications for every user, like e-mail, bittorrent, and a basic I2P Site for
you to personalize and share.
</p>

2
i2p2www/pages/downloads/post-install.html
View File

@@ -32,5 +32,5 @@ as the default settings of 96 KBps down / 40 KBps up are fairly slow.
{%- endtrans %}</p>
<p>{% trans browserconfig=site_url('about/browser-config') -%}
If you want to reach I2P sites via your browser, have a look on the <a href="{{ browserconfig }}">browser proxy setup</a> page for an easy howto.
If you want to reach I2P Sites via your browser, have a look on the <a href="{{ browserconfig }}">browser proxy setup</a> page for an easy howto.
{%- endtrans %}</p>

2
i2p2www/pages/downloads/windows.html
View File

@@ -169,7 +169,7 @@ configuration wizard.{%- endtrans %}
<p>{% trans -%}If you want to re-run the welcome wizard after completing it, you can visit the page
on{%- endtrans %} <a href="http://localhost:7657/welcome">your router console</a>.</p>
<p>{% trans -%}That's it! You're now ready to use I2P. You can browse I2P sites, download files, host services,
<p>{% trans -%}That's it! You're now ready to use I2P. You can browse I2P Sites, download files, host services,
e-mail and chat anonymously. Visit the <a href="https://localhost:7657/home">router console homepage</a> to
get started.{%- endtrans %}</p>

4
i2p2www/pages/site/browser/intro.html
View File

@@ -28,11 +28,11 @@
</h2>
<p>
{% trans bname=browser_name(), bsuff=browser_postname() %}{{ bname }} {{ bsuff }} is an easy-to-use bundle
that provides a streamlined way to use I2P applications and to browse I2P sites.
that provides a streamlined way to use I2P applications and to browse I2P Sites.
Although it can provide access to the regular internet via an outproxy, it also
integrates secure decentralized browsing, file sharing, and e-mail.{% endtrans %}
</p>
<img class="screenshot" src="{{ url_for('static', filename='images/browser/screenshots/2-I2P site.png') }}" />
<img class="screenshot" src="{{ url_for('static', filename='images/browser/screenshots/2-I2P Site.png') }}" />
<h2 id="landing">
<span class="permalink">

6
i2p2www/pages/site/docs/api/i2ptunnel.html
View File

@@ -24,8 +24,8 @@ A web interface for I2PTunnel management is avaliable on
<b>I2P Webserver</b> - A tunnel pointed to a Jetty webserver run
on <a href="http://localhost:7658">localhost:7658</a> for convenient and quick hosting on I2P.
<br>The document root is:{% endtrans %}
<br><b>Unix</b> - $HOME/.i2p/I2P site/docroot
<br><b>Windows</b> - %LOCALAPPDATA%\I2P\I2P site\docroot, which expands to: C:\Users\**username**\AppData\Local\I2P\I2P site\docroot
<br><b>Unix</b> - $HOME/.i2p/I2P Site/docroot
<br><b>Windows</b> - %LOCALAPPDATA%\I2P\I2P Site\docroot, which expands to: C:\Users\**username**\AppData\Local\I2P\I2P Site\docroot
</li>
</ul>
<h3 id="default-client-tunnels">{% trans %}Client tunnels{% endtrans %}</h3>
@@ -177,7 +177,7 @@ Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a
<p>{% trans -%}
Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying
capabilities. An example application would be a web application that does client-type
requests, or loopback-testing an I2P site as a diagnostic tool.
requests, or loopback-testing an I2P Site as a diagnostic tool.
{%- endtrans %}</p>
<h3 id="server-mode-irc">IRC Server</h3>

2
i2p2www/pages/site/docs/applications/embedding.html
View File

@@ -309,7 +309,7 @@ It could cause great harm both to our network and our reputation.
<h3>{% trans %}Join Us{% endtrans %}</h3>
<p>{% trans -%}
This may be obvious, but join the community. Run I2P 24/7. Start an I2P site about your project.
This may be obvious, but join the community. Run I2P 24/7. Start an I2P Site about your project.
Hang out in IRC #i2p-dev. Post on the forums. Spread the word.
We can help get you users, testers, translators, or even coders.
{%- endtrans %}</p>

2
i2p2www/pages/site/docs/discussions/naming.html
View File

@@ -196,7 +196,7 @@ the issues of conflicts and hijacking, however.
<p>{% trans -%}
<b>Awkward, not real-time:</b>
It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers,
I2P site status reporters.
I2P Site status reporters.
Jump servers and subscriptions are a pain, it should just work like DNS.
{%- endtrans %}</p>
<p>{% trans -%}

4
i2p2www/pages/site/docs/discussions/netdb.html
View File

@@ -161,7 +161,7 @@ the netDb.
I2P's netDb is very different from traditional load bearing DHTs - it only
carries network metadata, not any actual payload, which is why even a netDb
using a floodfill algorithm will be able to sustain an arbitrary amount of
I2P site/IRC/bt/mail/syndie/etc data. We can even do some optimizations as I2P
I2P Site/IRC/bt/mail/syndie/etc data. We can even do some optimizations as I2P
grows to distribute that load a bit further (perhaps passing bloom filters
between the netDb participants to see what they need to share), but it seems we
can get by with a much simpler solution for now.
@@ -299,7 +299,7 @@ The code now avoids peers that are shitlisted, failing, or not heard from in
half an hour, if possible.
</ol>
<p>
One benefit is faster first contact to an I2P site (i.e. when you had to fetch
One benefit is faster first contact to an I2P Site (i.e. when you had to fetch
the leaseset first). The lookup timeout is 10s, so if you don't start out by
asking a peer that is down, you can save 10s.

2
i2p2www/pages/site/docs/how/intro.html
View File

@@ -25,7 +25,7 @@ even taken over to attempt more malicious attacks.
<p>{% trans i2ptunnel=site_url('docs/api/i2ptunnel') -%}
The network itself is message oriented - it is essentially a secure and anonymous IP layer, where
messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP
packets. Some example uses of the network include "I2P sites" (webservers hosting normal web
packets. Some example uses of the network include "I2P Sites" (webservers hosting normal web
applications within I2P), a BitTorrent client ("I2PSnark"), or a distributed data store. With the
help of the <a href="{{ i2ptunnel }}">I2PTunnel</a> application, we are able to stream traditional
TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people

2
i2p2www/pages/site/docs/how/network-database.html
View File

@@ -836,7 +836,7 @@ by creating a small number (8-15) of floodfill routers clustered closely in the
and distribute the RouterInfos for these routers widely.
Then, all lookups and stores for a key in that keyspace would be directed
to one of the attacker's routers.
If successful, this could be an effective DOS attack on a particular I2P site, for example.
If successful, this could be an effective DOS attack on a particular I2P Site, for example.
{%- endtrans %}</p>
<p>{% trans -%}

10
i2p2www/pages/site/docs/how/tech-intro.html
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>

4
i2p2www/pages/site/docs/how/threat-model.html
View File

@@ -231,7 +231,7 @@ However, the attack is still possible, for example by an observer at
a large ISP or an Internet exchange point.
Those who want to defend against it
would want to take appropriate countermeasures, such as
setting low bandwidth limits, and using unpublished or encrypted leasesets for I2P sites.
setting low bandwidth limits, and using unpublished or encrypted leasesets for I2P Sites.
Other countermeasures, such as nontrivial delays and restricted routes, are
not currently implemented.
{%- endtrans %}</p>
@@ -323,7 +323,7 @@ Limits on the number of tunnels routed through a single peer
Prevention of peers from the same /16 IP range from being members of a single tunnel
{%- endtrans %}</li>
<li>{% trans -%}
For I2P sites or other hosted services, we support
For I2P Sites or other hosted services, we support
simultaneous hosting on multiple routers, or
<a href="#intersection">multihoming</a>
{%- endtrans %}</li>

4
i2p2www/pages/site/docs/naming.html
View File

@@ -165,7 +165,7 @@ For more information see the <a href="{{ namingdiscussion }}#alternatives">alter
<p>{% trans -%}
The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'.
Otherwise, it forwards the request to a configured HTTP outproxy.
Thus, in practice, all HTTP (I2P site) hostnames must end in the pseudo-Top Level Domain '.i2p'.
Thus, in practice, all HTTP (I2P Site) hostnames must end in the pseudo-Top Level Domain '.i2p'.
{%- endtrans %}</p>
<p>{% trans i2ptld='https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/',
@@ -337,7 +337,7 @@ See <a href="/spec/subscription">the specification</a> for details.
<h3>{% trans %}Outgoing Subscriptions{% endtrans %}</h3>
<p>{% trans -%}
Addressbook will publish the merged hosts.txt to a location
(traditionally hosts.txt in the local I2P site's home directory) to be accessed by others
(traditionally hosts.txt in the local I2P Site's home directory) to be accessed by others
for their subscriptions.
This step is optional and is disabled by default.
{%- endtrans %}</p>

4
i2p2www/pages/site/docs/tunnels/unidirectional.html
View File

@@ -82,7 +82,7 @@ The paper's main point is that
deanonymizations on unidirectional tunnels take a longer time, which is an
advantage, but that an attacker can be more certain in the unidirectional case.
Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least
with long-living I2P sites.
with long-living I2P Sites.
{%- endtrans %}</p>
<p>{% trans -%}
@@ -97,7 +97,7 @@ This conclusion is based on an arbitrary certainty vs. time weighting
(tradeoff) that may not be applicable in all cases. For
example, somebody could make a list of possible IPs then issue subpoenas to
each. Or the attacker could DDoS each in turn and via a simple
intersection attack see if the I2P site goes down or is slowed down. So close
intersection attack see if the I2P Site goes down or is slowed down. So close
may be good enough, or time may be more important.
{%- endtrans %}</p>

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

@@ -7,20 +7,20 @@
</li>
<li><a href="#systems">{% trans %}What systems will I2P run on?{% endtrans %}</a></li>
<li><a href="#java">{% trans %}Is installing Java required to use I2P?{% endtrans %}</a></li>
<li><a href="#I2P site">{% trans %}Whats an "I2P site" and how do I configure my browser so I can use them?{% endtrans %}</a></li>
<li><a href="#I2P Site">{% trans %}Whats an "I2P Site" and how do I configure my browser so I can use them?{% endtrans %}</a></li>
<li><a href="#active">{% trans %}What do the Active x/y numbers mean in the router console?{% endtrans %}</a></li>
<li><a href="#peers">{% trans %}My router has very few active peers, is this OK?{% endtrans %}</a></li>
<li><a href="#badcontent">{% trans %}I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?{% endtrans %}</a></li>
<li><a href="#blocking">{% trans %}Is it possible to block I2P?{% endtrans %}</a></li>
<li><a href="#protocolfamily">{% trans %}In <code>wrapper.log</code> I see an error stating <code>Protocol family unavailable</code> when I2P is loading{% endtrans %}</a></li>
<li><a href="#down">{% trans %}Most of the I2P sites within I2P are down?{% endtrans %}</a></li>
<li><a href="#down">{% trans %}Most of the I2P Sites within I2P are down?{% endtrans %}</a></li>
<li><a href="#port32000">{% trans %}Why is I2P listening for connections on port 32000?{% endtrans %}</a></li>
<li style="list-style: none; display: inline">
<h4>{{ _('Configuration') }}</h4>
</li>
<li><a href="#browserproxy">{% trans %}How do I configure my browser?{% endtrans %}</a></li>
<li><a href="#irc">{% trans %}How do I connect to IRC within I2P?{% endtrans %}</a></li>
<li><a href="#myI2P site">{% trans %}How do I set up my own I2P site?{% endtrans %}</a></li>
<li><a href="#myI2P Site">{% trans %}How do I set up my own I2P Site?{% endtrans %}</a></li>
<li><a href="#hosting">{% trans %}If I host a website at I2P at home, containing only HTML and CSS, is it dangerous?{% endtrans %}</a></li>
<li><a href="#addresses">{% trans %}How Does I2P find ".i2p" websites?{% endtrans %}</a></li>
<li><a href="#addressbook">{% trans %}How do I add to the AddressBook?{% endtrans %}</a></li>
@@ -97,11 +97,11 @@ While the main I2P client implementation requires Java, there are several
<a href="{{ alt }}">alternative clients</a> which don't require Java.
{%- endtrans %}</p>
<h3 id="I2P site"><span class="permalink"><a href="#I2P site">
<h3 id="I2P Site"><span class="permalink"><a href="#I2P Site">
{% trans %}What is an "I2P Site?"{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
Formerly called an eepSite, an I2P site is a website that is hosted anonymously, a hidden service which is accessible through your web browser.
Formerly called an eepSite, an I2P Site is a website that is hosted anonymously, a hidden service which is accessible through your web browser.
It can be accessed by setting your web browser's HTTP proxy to use the I2P web proxy (typically it listens on localhost port 4444), and browsing to the site.
{%- endtrans %}</p>
@@ -186,13 +186,13 @@ click <em>Shutdown</em>, wait 11 minutes, then start I2P.
{%- endtrans %}</p>
<h3 id="down"><span class="permalink"><a href="#down">
{% trans %}Most of the I2P sites within I2P are down?{% endtrans %}</a></span>
{% trans %}Most of the I2P Sites within I2P are down?{% endtrans %}</a></span>
</h3>
<p>{% trans eepstatus='http://'+i2pconv('identiguy.i2p') -%}
If you consider every I2P site that has ever been created, yes, most of them are down.
People and I2P sites come and go.
A good way to get started in I2P is check out a list of I2P sites that are currently up.
<a href="{{ eepstatus }}">{{ eepstatus }}</a> tracks active I2P sites.
If you consider every I2P Site that has ever been created, yes, most of them are down.
People and I2P Sites come and go.
A good way to get started in I2P is check out a list of I2P Sites that are currently up.
<a href="{{ eepstatus }}">{{ eepstatus }}</a> tracks active I2P Sites.
{%- endtrans %}</p>
<h3 id="port32000"><span class="permalink"><a href="#port32000">
@@ -232,8 +232,8 @@ Weechat users can use the following command to add a new network:
</pre>
</code>
<h3 id="myI2P site"><span class="permalink"><a href="#myI2P site">
{% trans %}How do I set up my own I2P site?{% endtrans %}</a></span>
<h3 id="myI2P Site"><span class="permalink"><a href="#myI2P Site">
{% trans %}How do I set up my own I2P Site?{% endtrans %}</a></span>
</h3>
<p>{% trans -%}
Click on the <a href="http://localhost:7658/">Website</a> link at the top of your router console for instructions.
@@ -251,7 +251,7 @@ yourself from a real threat will take real consideration in any case.{% endtrans
<p>The I2P Addressbook application maps human-readable names to long-term destinations, associated with services, making it more like a hosts file or a contact list than a network database or a DNS service. It's also local-first there is no recognized global namespace, you decide what any given .i2p domain maps to in the end. The middle-ground is something called a "Jump Service" which provides a human-readable name by redirecting you to a page where you will be asked "Do you give the I2P router permission to call $SITE_CRYPTO_KEY the name $SITE_NAME.i2p" or something to that effect. Once it's in your addressbook, you can generate your own jump URL's to help share the site with others. </p>
<h3 id="addressbook">{% trans %}How do I add addresses to the Addressbook? {% endtrans %}</h3>
<p>{% trans %}You cannot add an address without knowing at least the base32 or base64 of the site you want to visit. The "hostname" which is human-readable is only an alias for the cryptographic address, which corresponds to the base32 or base64. Without the cryptographic address, there is no way to access an I2P site, this is by design. Distributing the address to people who do not know it yet is usually the responsibility of the Jump service provider. Visiting an I2P site which is unknown will trigger the use of a Jump service. stats.i2p is the most reliable Jump service.{% endtrans %}</p>
<p>{% trans %}You cannot add an address without knowing at least the base32 or base64 of the site you want to visit. The "hostname" which is human-readable is only an alias for the cryptographic address, which corresponds to the base32 or base64. Without the cryptographic address, there is no way to access an I2P Site, this is by design. Distributing the address to people who do not know it yet is usually the responsibility of the Jump service provider. Visiting an I2P Site which is unknown will trigger the use of a Jump service. stats.i2p is the most reliable Jump service.{% endtrans %}</p>
<p>{% trans %}If you're hosting a site via i2ptunnel, then it won't have a registration with a jump service yet. To give it a URL locally, then visit the configuration page and click the button that says "Add to Local Addressbook." Then go to http://127.0.0.1:7657/dns to look up the addresshelper URL and share it.{% endtrans %}</p>
@@ -440,7 +440,7 @@ These are described in detail below.
7658
</td>
<td>
Your <a href="http://127.0.0.1:7658">I2P site</a>
Your <a href="http://127.0.0.1:7658">I2P Site</a>
</td>
<td>
{% trans -%}May be disabled in the <code>clients.config</code> file.

2
i2p2www/pages/site/get-involved/develop/applications.html
View File

@@ -207,7 +207,7 @@ to and from I2P. At this point in time it lacks UDP support, but UDP support
is planned in the near future. BOB also contains several tools, such as
destination key generation, and verification that an address conforms to
I2P specifications. Up to date info and applications that use BOB can be
found at this <a href="http://{{ boburl }}/">I2P site</a>.
found at this <a href="http://{{ boburl }}/">I2P Site</a>.
{%- endtrans %}</p>

4
i2p2www/pages/site/get-involved/develop/signed-keys.html
View File

@@ -15,7 +15,7 @@ signature for his key.
</ol>
<h3 id="monotone-keys-for-zzz">{{ _('Monotone keys for zzz') }}</h3>
<p>{% trans -%}
<u>Tip:</u> To find zzz's GPG key, on his I2P site locate the key `0xA76E0BED`, with
<u>Tip:</u> To find zzz's GPG key, on his I2P Site locate the key `0xA76E0BED`, with
the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155
76BA A76E 0BED`.
{%- endtrans %}</p>
@@ -79,7 +79,7 @@ the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155
<h3 id="monotone-keys-for-complication">{{ _('Monotone keys for Complication') }}</h3>
<p>{% trans -%}
<b>Tip:</b> To find Complication's GPG key, on his I2P site locate the key
<b>Tip:</b> To find Complication's GPG key, on his I2P Site locate the key
`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF
2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`.
{%- endtrans %}</p>

2
i2p2www/pages/site/get-involved/guides/new-translators.html
View File

@@ -120,7 +120,7 @@ There are about 15 files in the i2p.i2p branch that needs translation:
<li>
<code>apps/routerconsole/jsp/help_xx.jsp</code></li>
<li>
<code>installer/resources/I2P site.help/help/index_xx.html</code></li>
<code>installer/resources/I2P Site.help/help/index_xx.html</code></li>
<li>
<code>apps/i2ptunnel/locale/messages_xx.po</code></li>
<li>

2
i2p2www/pages/site/get-involved/guides/reseed.html
View File

@@ -191,7 +191,7 @@ Optional:
<p>
This How-to is tested with Ubuntu/Debian as well as FreeBSD.
The web server has to be public reachable from all over the world, an I2P site inside I2P can be setup in addition.
The web server has to be public reachable from all over the world, an I2P Site inside I2P can be setup in addition.
Also frequent or infrequent attempts to scrape all your reseed files, and of course attacks on your server.
The web server doesn't need to listen at default SSL/TLS port 443 - any other port can be used for obfuscation.
</p>

6
i2p2www/pages/site/get-involved/roadmap.html
View File

@@ -178,7 +178,7 @@ Update onboarding information in router console readme
</li><li>
Operators guides for reseed services
</li><li>
Revise CSS on the default I2P site to resemble console Light theme
Revise CSS on the default I2P Site to resemble console Light theme
</li><li>
Windows Installer "Install as Windows Service" bugfixes and improvements.
</li><li>
@@ -448,7 +448,7 @@ IPv6 address selection improvements
</li><li>
Better tunnel peer selection for hidden and IPv6-only modes
</li><li>
Prep for HTTPS console and I2P site by default
Prep for HTTPS console and I2P Site by default
</li><li>
Prep for splitting up Debian package
</li><li>
@@ -467,7 +467,7 @@ Tomcat 8.5.30
</li><li>
Susimail folders, background sending
</li><li>
Improved support for SSL console and I2P site
Improved support for SSL console and I2P Site
</li><li>
Bug fixes, translation updates, geoip updates
</li><li>

6
i2p2www/pages/site/misc/i2ptunnel-migration.html
View File

@@ -6,7 +6,7 @@
<p>{% trans -%}
After upgrading to the new architecture, you'll have to do a
little work to get your old I2PTunnel-driven servers running.
Lets walk through a simple example. For an I2P site with the
Lets walk through a simple example. For an I2P Site with the
old clientApp configuration, you had:
{%- endtrans %}</p>
<pre>
@@ -18,8 +18,8 @@ old clientApp configuration, you had:
<li>{% trans url='http://localhost:7657/i2ptunnel/' %}Jump to <a href="{{ url }}">{{ url }}</a>{% endtrans %}</li>
<li>{% trans %}Click on Add new: [Server tunnel] "GO"{% endtrans %}</li>
<li><ul>
<li>{% trans %}For the name: <code>"I2P site"</code>{% endtrans %}</li>
<li>{% trans %}For the description: <code>"My I2P site, isn't it pretty?"</code>{% endtrans %}</li>
<li>{% trans %}For the name: <code>"I2P Site"</code>{% endtrans %}</li>
<li>{% trans %}For the description: <code>"My I2P Site, isn't it pretty?"</code>{% endtrans %}</li>
<li{% trans %}>For the target host:{% endtrans %} <code>localhost</code></li>
<li>{% trans %}For the target port:{% endtrans %} <code>80</code></li>
<li>{% trans -%}

2
i2p2www/pages/site/misc/i2ptunnel-services.html
View File

@@ -2,7 +2,7 @@
{% block title %}{% trans %}I2PTunnel services{% endtrans %}{% endblock %}
{% block content %}
<p>{% trans -%}
Below is quick copy of aum's I2P site deployment guide.
Below is quick copy of aum's I2P Site deployment guide.
{%- endtrans %}</p>
<strong>{% trans %}1. - Deploy a local server{%- endtrans %}</strong>

24
i2p2www/pages/site/misc/ticket919.html
View File

@@ -11,17 +11,17 @@ with version 0.9.5. Other operating systems are not affected.
<h2>Background</h2>
<p>A change was introduced during the 0.9.5 cycle to allow I2P's configuration files to be edited with the standard
Windows text editor, <code>Notepad</code>. This change had the unfortunate side-effect of causing our I2P site migration code to
fail to run on Windows systems, leading to I2P sites being served from the installation directory. Consequently:
Windows text editor, <code>Notepad</code>. This change had the unfortunate side-effect of causing our I2P Site migration code to
fail to run on Windows systems, leading to I2P Sites being served from the installation directory. Consequently:
</p>
<ul>
<li>depending upon how I2P is started, the I2P site may not be accessible; and</li>
<li>confusion ensues&mdash;all documentation states that I2P sites are served from the profile path; and</li>
<li>depending upon how I2P is started, the I2P Site may not be accessible; and</li>
<li>confusion ensues&mdash;all documentation states that I2P Sites are served from the profile path; and</li>
<li>the update to Jetty 7, included in the 0.9.6 release, will fail.</li>
</ul>
<p>While no action is required for users that are not hosting an I2P site (or are not using the included Jetty to host an I2P site), it is
recommended to follow this procedure to avoid issues in case you decide to run a Jetty-hosted I2P site in the future. If you are running an
I2P site it is important to follow this procedure prior to upgrading to 0.9.6.
<p>While no action is required for users that are not hosting an I2P Site (or are not using the included Jetty to host an I2P Site), it is
recommended to follow this procedure to avoid issues in case you decide to run a Jetty-hosted I2P Site in the future. If you are running an
I2P Site it is important to follow this procedure prior to upgrading to 0.9.6.
</p>
<p>
@@ -46,20 +46,20 @@ I2P site it is important to follow this procedure prior to upgrading to 0.9.6.
You should see something like the following:
<a href="{{ url_for('static', filename='images/ticket919/paths.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/paths.png') }}" /></a>
If the path at number 1 in the image above is set to <code>I2P site/jetty.xml</code>, the path needs to be updated.
If the path at number 1 in the image above is set to <code>I2P Site/jetty.xml</code>, the path needs to be updated.
</li>
<li>Click the <code>Edit</code> button next to <em>I2P webserver (I2P site)</em>. The page will reload to allow the path to be edited as shown below:
<li>Click the <code>Edit</code> button next to <em>I2P webserver (I2P Site)</em>. The page will reload to allow the path to be edited as shown below:
<a href="{{ url_for('static', filename='images/ticket919/edit.png') }}">
<img alt="" style="padding:10px;margin-left:auto;margin-right:auto;display:block" src="{{ url_for('static', filename='images/ticket919/edit.png') }}" /></a>
Insert the full path to your I2P configuration directory <em>before</em> the text "I2P site/jetty.xml" as shown above,
Insert the full path to your I2P configuration directory <em>before</em> the text "I2P Site/jetty.xml" as shown above,
then click Click the <code>Save Client Configuration</code> button.
</li>
<li> If you're hosting an I2P site, move its contents to its proper home at <code>%APPDATA%\I2P\I2P site\docroot</code>.
<li> If you're hosting an I2P Site, move its contents to its proper home at <code>%APPDATA%\I2P\I2P Site\docroot</code>.
</li>
<li>At this point you should restart your I2P router.</li>
</ol>
<p>After following the steps outlined above, your I2P site will be served from <code>%APPDATA%\I2P\I2P site\docroot</code>
<p>After following the steps outlined above, your I2P Site will be served from <code>%APPDATA%\I2P\I2P Site\docroot</code>
and should be accessible at <a href="http://127.0.0.1:7658">http://127.0.0.1:7658</a>.
</p>
{% endblock %}