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

Make usage of 2-word Address Book consistent across website, except preserve old blog posts as is

Browse Source
This commit is contained in:
idk
2021-01-23 21:06:01 -05:00
parent 8c3bfb60ec
commit 8891b5e8c0
12 changed files with 63 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
i2p2www/pages/global/nav.html
View File

@ -151,7 +151,7 @@
<li><a href="{{ site_url('docs/tunnels/old-implementation') }}"><div class="menuitem"><span>{{ _('Old implementation') }}</span></div></a></li>
</ul>
</li>
<li><a href="{{ site_url('docs/naming') }}"><div class="menuitem"><span>{{ _('Naming and addressbook') }}</span></div></a></li>
<li><a href="{{ site_url('docs/naming') }}"><div class="menuitem"><span>{{ _('Naming and Address Book') }}</span></div></a></li>
<li><a href="{{ site_url('docs/plugins') }}"><div class="menuitem"><span>{{ _('Plugins') }}</span></div></a></li>
</ul>
</li>

2
i2p2www/pages/site/about/software.html
View File

@ -40,7 +40,7 @@ allow you to use those human-readable addresses in place of those I2P
addresses. It is more similar to a hosts file or a contact list than a network
database or a DNS service. There is no recognized global namespace, you decide
what any given .i2p domain maps to in the end.{%- endtrans %}</p>
<p><strong>The QR Code Generator</strong>: Besides the Addressbook, I2P
<p><strong>The QR Code Generator</strong>: Besides the Address Book, I2P
addresses can be shared by converting them into QR codes and scanning them with
a camera. This is especially useful for Android devices.</p>
<p>{% trans i2ptunnel=site_url('docs/api/i2ptunnel') -%}<strong><a href="{{ i2ptunnel }}">I2P Hidden Services Manager</a></strong> This is a general-purpose

4
i2p2www/pages/site/docs/how/tech-intro.html
View File

@ -834,7 +834,7 @@ SYN, FIN, RST, etc).
<h2 id="app.naming">{% trans %}Naming library and address book{% endtrans %}</h2>
<p><i>{% trans naming=site_url('docs/naming') -%}
For more information see the <a href="{{ naming }}">Naming and Addressbook</a> page.
For more information see the <a href="{{ naming }}">Naming and Address Book</a> page.
{%- endtrans %}</i></p>
<p><i>{% trans dev='mihi, Ragnarok' -%}Developed by: {{ dev }}{%- endtrans %}</i></p>
@ -846,7 +846,7 @@ inherent demand for secure communication and decentralized operation, the
traditional DNS-style naming system is clearly out, as are "majority rules"
voting systems. Instead, I2P ships with a generic naming library and a base
implementation designed to work off a local name to destination mapping, as
well as an optional add-on application called the "addressbook". The addressbook
well as an optional add-on application called the "Address Book". The address book
is a web-of-trust-driven secure, distributed, and human readable naming system,
sacrificing only the call for all human readable names to be globally unique
by mandating only local uniqueness. While all messages in I2P are cryptographically

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

@ -39,8 +39,8 @@ If you find any inaccuracies in the documents linked below, please
<h3>{% trans %}Application-Layer Topics{% endtrans %}</h3>
<ul>
<li><a href="{{ site_url('get-involved/develop/applications') }}">Application Development Overview and Guide</a></li>
<li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Addressbook') }}</a></li>
<li><a href="{{ spec_url('subscription') }}">{{ _('Addressbook Subscription Feed Commands') }}</a></li>
<li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Address Book') }}</a></li>
<li><a href="{{ spec_url('subscription') }}">{{ _('Address Book Subscription Feed Commands') }}</a></li>
<li><a href="{{ site_url('docs/plugins') }}">{{ _('Plugins Overview') }}</a></li>
<li><a href="{{ spec_url('plugin') }}">{{ _('Plugin Specification') }}</a></li>
<li><a href="{{ site_url('docs/applications/managed-clients') }}">{{ _('Managed Clients') }}</a></li>

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

@ -1,5 +1,5 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Naming and Addressbook{% endtrans %}{% endblock %}
{% block title %}{% trans %}Naming and Address Book{% endtrans %}{% endblock %}
{% block lastupdated %}2020-07{% endblock %}
{% block accuratefor %}0.9.46{% endblock %}
{% block content %}
@ -180,7 +180,7 @@ an error page to the user with links to several "jump" services.
See below for details.
{%- endtrans %}</p>
<h2 id="addressbook">{% trans %}Addressbook{% endtrans %}</h2>
<h2 id="addressbook">{% trans %}Address Book{% endtrans %}</h2>
<h3>{% trans %}Incoming Subscriptions and Merging{% endtrans %}</h3>
<p>{% trans -%}
@ -336,7 +336,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
Address Book 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
for their subscriptions.
This step is optional and is disabled by default.

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

@ -248,12 +248,12 @@ Tahoe-LAFS, but they require additional set up and are only appropriate for some
yourself from a real threat will take real consideration in any case.{% endtrans %}</p>
<h3 id="addresses">{% trans %}How Does I2P find ".i2p" websites? {% endtrans %}</h3>
<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>
<p>The I2P Address Book 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 address book, 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>
<h3 id="addressbook">{% trans %}How do I add addresses to the Address Book? {% 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 %}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>
<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 Address Book." Then go to http://127.0.0.1:7657/dns to look up the addresshelper URL and share it.{% endtrans %}</p>
<h3 id="ports"><span class="permalink"><a href="#ports">
{% trans %}What ports does I2P use?{% endtrans %}</a></span>
@ -536,7 +536,7 @@ This question can be answered in 3 parts:
{%- endtrans %}</p>
<ol>
<li>{% trans -%}My router often displays a message saying "Website Not Found In Addressbook", why do I see this message?{%- endtrans %}
<li>{% trans -%}My router often displays a message saying "Website Not Found In Address Book", why do I see this message?{%- endtrans %}
<p>{% trans -%}Human-readable addresses such as <i>http://website.i2p</i> are references to a long, random string known as a <b>destination</b>.
These references are registered and stored at address book services such as stats.i2p, which is run by zzz.
You will often encounter a "b32" address. A "b32" is a hash (specifically, a <a href="https://en.wikipedia.org/wiki/SHA-2">SHA256</a> hash) of the

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

@ -131,7 +131,7 @@ to what licenses meet the above four guarantees for inclusion in the I2P distrib
<td valign="top" align="left">zzz</td>
</tr>
<tr>
<td valign="top" align="left"><b>Addressbook</b></td>
<td valign="top" align="left"><b>Address Book</b></td>
<td valign="top" align="left">apps/addressbook</td>
<td valign="top" align="left">addressbook.war</td>

2
i2p2www/pages/spec/index.html
View File

@ -61,6 +61,6 @@ These will eventually be migrated to the new specifications system.
<li><a href="{{ site_url('docs/api/samv3') }}">SAM v3</a></li>
<li><a href="{{ site_url('docs/api/bob') }}">BOB</a></li>
<li><a href="{{ site_url('docs/applications/bittorrent') }}">{{ _('Bittorrent') }}</a></li>
<li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Addressbook') }}</a></li>
<li><a href="{{ site_url('docs/naming') }}">{{ _('Naming and Address Book') }}</a></li>
</ul>
{% endblock %}