mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-18 23:53:42 +02:00
Moneropedia: Remove two I1P-related entries: 'Address Book' and 'Destination'
This commit is contained in:
erciccione
parent
693eab2bf3
commit
513658d591
@ -1,34 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -709,7 +709,6 @@ moneropedia:
|
||||
back: Back to the Moneropedia
|
||||
entries:
|
||||
account: Account
|
||||
address-book: Address Book
|
||||
address: Address
|
||||
airgap: Airgap
|
||||
atomic-units: Atomic Units
|
||||
@ -725,7 +724,6 @@ moneropedia:
|
||||
cryptocurrency: Cryptocurrency
|
||||
daemon: Daemon
|
||||
denominations: Denominations
|
||||
destination: Destination
|
||||
encryption: Encryption
|
||||
fluffyblocks: Fluffy Blocks
|
||||
fungibility: Fungibility
|
||||
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book", "carnet-d'adresses"]
|
||||
summary: "Vous permet de visiter des sites et services I2P du domaine .i2p"
|
||||
---
|
||||
|
||||
### Les Bases
|
||||
|
||||
Afin de naviguer sur des sites @I2P ou de consulter des services avec @Kovri, vous aurez besoin d'un carnet d'adresses. Un carnet d'adresses vous permettra de traduire les sites et services @I2P qui utilisent le [domaine de premier niveau](https://fr.wikipedia.org/wiki/Domaine_de_premier_niveau) `.i2p` en adresses que le réseau @I2P comprendra.
|
||||
|
||||
Sans carnet d'adresse, vous seriez contraint d'utiliser une @adresse-base32 chaque fois que vous visiteriez un site ou service @I2P, et ce n'est pas drôle !
|
||||
|
||||
### Informations détaillées
|
||||
|
||||
Comme [DNS](https://fr.wikipedia.org/wiki/Domain_Name_System) n'existe pas sur le réseau @I2P, @Kovri **ne peut pas** utiliser DNS ou quelque sorte de résolution d'@hôte-canonique-unique. Au lieu de cela, @Kovri fait correspondre un @hôte-unique-localement à une @adresse-base64 de @destination dans une @souscription. Une fois que votre carnet d'adresse est complété avec une @souscription, vous pouvez résoudre vos sites favoris du domaine `.i2p` en une adresse destination @I2P utilisable.
|
||||
|
||||
### Créer un carnet d'adresses
|
||||
|
||||
Par défaut, votre installation contiendra une @souscription publique par défaut appelée `hosts.txt` dans votre @répertoire-de-données. Au démarrage de @Kovri, il chargera cette souscription et récupèrera toute autre souscription que vous aurez spécifié. Une fois chargé, votre carnet d'adresses sera correctement rempli. Pour des détails sur la gestion des souscriptions, voir @souscription.
|
||||
|
||||
### Mettre à jour le carnet d'adresses
|
||||
|
||||
Actuellement, il y a plusieurs façons de mettre à jour votre carnet d'adresses :
|
||||
|
||||
1. Utiliser un @service-de-rebond pour insérer des adresses I2P dans votre carnet d'adresses
|
||||
2. Utiliser un @service-de-rebond pour copier/coller une adresse dans votre @souscription privée
|
||||
3. Ajouter ou supprimer manuellement depuis une @souscription privée
|
||||
|
||||
**Remarque : Kovri est en cours de développement intensif. Dans le futur il y *aura* des moyens plus simples de mettre à jour le carnet d'adresses**
|
||||
|
||||
### Spécifications du carnets d'adresse / du nommage
|
||||
|
||||
Pour des spécifications détaillées et plus encore, visiter les [Spécifications du carnet d'adresses et du nommage](https://geti2p.net/fr/docs/naming)
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "Une adresse sur le réseau qui sert comme point de terminaison (soit local, soit distant)."
|
||||
---
|
||||
|
||||
### Les Bases
|
||||
|
||||
Une @destination est l'adresse @interne-au-réseau @I2P du point de terminaison final auquel vous essayé de vous connecter (exemple : un site web, service, ou nœud Monero @I2P). Cela peut aussi inclure une *destination locale* à laquelle d'*autres* homologues doivent se connecter afin de prendre contact pour communiquer (de la même manière que sur le @réseau-en-clair, votre adresse IP est donnée à un site web lorsque vous vous connectez, de sorte qu'il sache *où* renvoyer les informations).
|
||||
|
||||
### Informations détaillées
|
||||
|
||||
Une destination @I2P peut être encodée en utilisant une @adresse-base32 ou une @adresse-base64. La plupart des utilisateurs ne s'intéresseront qu'aux @adresses-base32 ou aux noms d'hôtes `.i2p`, tandis que, en interne, @Kovri et le @carnet-d'adresses @I2P utilisent des @adresses-base64. Finalement, toutes les @destinations dans @I2P sont des clefs de 516 octets (ou plus) :
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Remarque : les certificats ne sont pas utilisés pour le moment, mais s'il l'étaient, les clefs seraient plus longues.
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,32 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book", "książka-adresowa", "książce-adresowej", "książki-adresowej", "książkę-adresową", "książki-adresowe"]
|
||||
summary: "Pozwala na odwiedzanie stron/serwisów w sieci I2P w domenie .i2p."
|
||||
---
|
||||
|
||||
### Podstawy
|
||||
|
||||
Aby przeglądać strony i serwisy w sieci @I2P przy użyciu @Kovri, potrzebujesz książki adresowej. Pozwoli ona na przetłumaczenie stron i serwisów I2P, które używają [domeny najwyższego poziomu] `.i2p` (https://en.wikipedia.org/wiki/Top_level_domain), na adres zrozumiały przez sieć I2P.
|
||||
|
||||
Bez książki adresowej musiałbyś używać @adresu-base32 za każdą wizytą na stronie sieci I2P, a to nie jest wcale zabawne!
|
||||
|
||||
### Szczegółowe informacje
|
||||
|
||||
Ponieważ [System Nazywania Domen](https://en.wikipedia.org/wiki/DNS) nie istnieje w sieci I2P, @Kovri również **nie używa** Systemu Nazywania Domen ani żadnego rodzaju rozwiązania @zasadniczego-unikalnego-hostu. Zamiast tego, Kovri łączy @lokalnie-unikalny-host z @adresem-base64 w @subskrypcji. Po wypełnieniu książki adresowej subskrypcją, możesz zamienić daną stronę o domenie `.i2p` na łatwą do użycia sieć I2P.
|
||||
|
||||
### Tworzenie książki adresowej
|
||||
|
||||
Domyślnie przy instalacji otrzymasz publiczną @subskrypcję o nazwie `hosts.txt` w @katalogu-danych. Po uruchomieniu, Kovri ładuje tę subskrypcję i przywołuje wszystkie pozostałe sprecyzowane subskrypcje. Po załadowaniu, twoja książka adresowa zostanie odpowiednio wypełniona. Po więcej szczegółów dotyczących zarządzania subykrypcjami, przejdź do @subsckrypcji.
|
||||
|
||||
### Aktualizowanie książki adresowej
|
||||
|
||||
Obecnie istnieje kilka sposobów na zaktualizowanie książki adresowej:
|
||||
1. Użyj @opcji-przeskakiwania, aby wpisać adres I2P do książki adresowej.
|
||||
2. Użyj @opcji-przeskakiwania, aby skopiować i wkleić adres do twojej prywatnej subskrypcji.
|
||||
3. Ręczniej dodaj lub odejmij z prywatnej subskrypcji.
|
||||
|
||||
**Uwaga: Kovri jest w trakcie rozwoju. W przyszłości *pojawią się* łatwiejsze sposoby na zaktualizowanie książki adresowej.**
|
||||
|
||||
### Specyfikacja książki adresowej/nazewnictwa
|
||||
|
||||
Aby dowiedzieć się więcej na temat specyfikacji, przejdź do [specyfikacji książki adresowej i nazewnictwa](https://geti2p.net/en/docs/naming).
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations", "węzeł-docelowy", "węzła-docelowego", "węźle-docelowym", "węzłów-docelowych"]
|
||||
summary: "Adres internetowy będący punktem końcowym, zarówno lokalnym jak i odległym."
|
||||
---
|
||||
|
||||
### Podstawy
|
||||
|
||||
Węzeł docelowy jest adresem końcowym sieci @I2P, z którym chcesz się połączyć, np. stroną internetową w sieci I2P, serwisem lub węzłem Monero. Może on także uwzględniać *węzeł docelowy lokalny*, którego pozostali użytkownicy także muszą się połączyć aby nawiązać komunikację (podobnie jak w @clearnecie twój adres IP jest przekazany stronie podczas połączenia, aby wiadomo było *dokąd* wysłać informacje zwrotne).
|
||||
|
||||
### Szczegółowe informacje
|
||||
|
||||
Węzeł docelowy I2P może być zakodowany w @adresie-base32 lub @adresie-base64. Większość użytkowników przejmie się jedynie adresem Base32 lub nazwą hosta `.i2p`, podczas gdy, wewnętrznie, @Kovri i @książka-adresowa korzystają z @adresu-base64. Ostatecznie wszystkie węzły docelowe w I2p są 516-bajtowymi kluczami (lub dłuższymi):
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Uwaga: certyfikaty nie zostały tu użyte, ale gdyby były, klucze byłyby jeszcze dłuższe.
|
||||
@ -1,34 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,18 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book", "адресная-книга", "адресной-книгой", "адресной-книги", "адресной-книге", "адресную-книгу", "адресная-книга"]
|
||||
summary: "Позволяет обозревать веб-сайты / службы I2P, имеющие домен .i2p"
|
||||
---
|
||||
|
||||
### Основная информация
|
||||
|
||||
Для того чтобы посещать сайты, использующие протокол @I2P, или получить доступ к службам через @Kovri, вам понадобится адресная книга. Адресная книга позволит вам переводить @I2P веб-сайты / службы, использующие [домен верхнего уровня](https://en.wikipedia.org/wiki/Top_level_domain).`i2p` в формат адресов, которые будут понятны сети I2P.
|
||||
|
||||
Без адресной книги вы будете испытывать неудобство, так как вам придётся использовать @адрес-Base32 всякий раз, когда вам понадобится @I2P веб-сайт / служба, что отнюдь не весело!
|
||||
|
||||
### Углублённая информация
|
||||
|
||||
Так как в @I2P сети отсутствует [DNS](https://en.wikipedia.org/wiki/DNS), Kovri также **не использует** DNS или какое-либо другое @канонически-уникальное-хост решение. Вместо этого Kovri соединяет @локально-уникальный-хост с @Base64-адресом @адресата в @подписке. Как только ваша адресная книга будет заполнена @подпиской, вы сможете раскрыть ваш любимый сайт домена `.i2p` по @I2P адресу назначения.
|
||||
|
||||
### Создание адресной книги
|
||||
|
||||
По умолчанию установка происходит с публичной @подпиской, используемой по умолчанию, которая в @директории-данных называется `hosts.txt`. При запуске @Kovri загружает эту подписку и выбирает любые другие подписки, которые были указаны вами. После загрузки ваша адресная книга будет заполнена надлежащим образом. Подробная информация по управлению подписками содержится в разделе @подписка.
|
||||
|
||||
### Обновление адресной книги
|
||||
|
||||
В настоящее время существует несколько способов обновления вашей адресной книги:
|
||||
|
||||
1. Используйте @jump-service чтобы занести I2P адреса в адресную книгу
|
||||
2. Используйте @jump-service, чтобы скопировать / вставить адрес в вашу приватную @подписку
|
||||
3. Вручную добавьте или извлеките адрес из приватной @подписки
|
||||
|
||||
**Примечание: Kovri проходит этап интенсивной разработки. В будущем *появятся* более простые способы обновления адресной книги.**
|
||||
|
||||
### Адресная книга / параметры наименования
|
||||
|
||||
Подробную и дополнительную информацию по этим параметрам можно найти по ссылке: [адресная книга и параметры наименования](https://geti2p.net/en/docs/naming).
|
||||
@ -1,19 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations", "назначения", "адрес-назначения"]
|
||||
summary: "Адрес в сети, который служит конечной точкой (локальной или удаленной)"
|
||||
---
|
||||
|
||||
{% include disclaimer.html translated="yes" translationOutdated="no" %}
|
||||
### Основная информация
|
||||
|
||||
Адрес @назначения является внутрисетевым @I2P @адресом-конечной-точки назначения, с которой вы пытаетесь соединиться (например, @I2P веб-сайтом, службой или узлом Monero).
|
||||
Также это может быть локальный *адрес назначения*, с *которым* одноранговые узлы соединяются для того, чтобы установить связь (подобно тому, как в @клирнете ваш IP-адрес даётся веб-сайту, когда вы устанавливаете с ним соединение, чтобы сайт знал, *куда* отправлять информацию).
|
||||
|
||||
### Углублённая информация
|
||||
|
||||
@I2P адрес назначения может быть закодирован как @адрес-Base32 или @адрес-Base64. Большинство пользователей использует только адреса Base32 или имя хоста `.i2p`, в то время как внутренне @адресная-книга @Kovri / @I2P использует @Base64-адреса. В конечном счёте все адреса назначения в @I2P используют ключи размером 516 байт (или больше):
|
||||
|
||||
`256-байт публичный ключ + 128-байт ключ подписи + нулевой сертификат = 516 байт in Base64 представление`
|
||||
|
||||
Примечание: Сертификаты уже не используются, но если бы они использовались, ключи были бы длиннее.
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,31 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
### 基础知识
|
||||
|
||||
为了使用@Kovri浏览@I2P站点或服务，您需要一个地址薄。这个地址薄将那些使用 `.i2p` [顶级域名](https://en.wikipedia.org/wiki/Top_level_domain)的地址,翻译成为一个@I2P网络(匿名网络)可以理解的地址。
|
||||
如果没有地址簿，每次访问@I2P网站/服务时，您将不得不使用@base32地址—这样可一点都不好玩!
|
||||
|
||||
### 深度信息
|
||||
|
||||
由于@I2P网络上不存在[DNS](https://en.wikipedia.org/wiki/DNS)， @Kovri也不使用DNS或任何类型的@标准唯一主机解析。相反，Kovri在@订阅中将@本地唯一主机与@base64地址@目标配对。一旦你的地址簿中填了一个@订阅，你就可以将你最喜欢的 `.i2p` 域站点转换为为可用的@I2P目标。
|
||||
|
||||
### 创建一个地址薄
|
||||
|
||||
默认情况下，在安装时在你的@数据词典里将带有一个名为 `hosts.txt` 的默认公共@订阅。当@Kovri启动时，它加载这个订阅并获取您指定的任何其他订阅。一旦加载，您的通讯录将被适当地填充。有关如何管理订阅的详细信息，请参见@订阅。
|
||||
|
||||
### 更新地址薄
|
||||
|
||||
目前，有几种方法可以更新你的地址薄:
|
||||
1. 使用@跳转服务，将I2P地址插入地址簿
|
||||
2. 使用@跳转服务，复制/粘贴一个地址到您的私有@订阅当中
|
||||
3. 从私有@订阅中，手动添加或删除
|
||||
|
||||
**注意:Kovri正在大力开发中。在未来，将有更容易的方法来更新通讯录**
|
||||
|
||||
### 地址薄 / 命名规范
|
||||
|
||||
有关规范详细信息及更多内容，请访问 [地址薄以及命名规范](https://geti2p.net/en/docs/naming)
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
### 基础知识
|
||||
|
||||
@目标指的是，您试图连接到的最终端点的@I2P @网内地址（例如:@I2P网站、服务或门罗币节点）。这也可以包括一个*本地目标*，这其中 *其它* 对等节点需要连接到这个*本地目标*，以便与之进行通信（类似于在@明网中，当您连到某个网站时，您的IP地址也会被发送到这个网站，因此它也知道把信息发回“哪里”）。
|
||||
|
||||
### 深度信息
|
||||
|
||||
一个@I2P目标可以被编码成@base32地址或@base64地址。大多数用户只关心@base32地址或一个 `.i2p` 。在内部，@Kovri / @I2P @地址薄使用@base64地址。最终，@I2P中的所有@目标都是516字节（或更长）的密钥:
|
||||
|
||||
`256字节公钥 + 128字节签名密钥 + 空证书 = 经Base64编码后表示为516字节`
|
||||
|
||||
注意:这是在不使用证书的情况下，如果使用证书，密钥会更长。
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Address-Book"]
|
||||
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||
|
||||
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||
|
||||
### In-depth information
|
||||
|
||||
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||
|
||||
### Creating an Address Book
|
||||
|
||||
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||
|
||||
### Updating the Address Book
|
||||
|
||||
Currently, there are several ways to update your address book:
|
||||
|
||||
1. Use a @jump-service to insert I2P addresses into your address book
|
||||
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||
3. Manually add or subtract from a private @subscription
|
||||
|
||||
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||
|
||||
### Address Book / Naming specification
|
||||
|
||||
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
tags: ["kovri"]
|
||||
terms: ["Destination", "Destinations"]
|
||||
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||
---
|
||||
|
||||
### The Basics
|
||||
|
||||
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||
|
||||
### In-depth Information
|
||||
|
||||
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||
|
||||
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||
|
||||
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||
@ -1,10 +0,0 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
title: titles.moneropedia
|
||||
entry: moneropedia.entries.address-book
|
||||
---
|
||||
|
||||
@moneropedia_article
|
||||
|
||||
{% t global.lang_tag %}
|
||||
{% tf resources/moneropedia/address-book.md %}
|
||||
@ -1,10 +0,0 @@
|
||||
---
|
||||
layout: moneropedia
|
||||
title: titles.moneropedia
|
||||
entry: moneropedia.entries.destination
|
||||
---
|
||||
|
||||
@moneropedia_article
|
||||
|
||||
{% t global.lang_tag %}
|
||||
{% tf resources/moneropedia/destination.md %}
|
||||
Loading…
Reference in New Issue
Block a user