Git-Mirrors/reticulum_website
1
0
Fork 0
mirror of https://github.com/markqvist/reticulum_website.git synced 2025-02-05 01:25:29 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated github build

Browse Source
This commit is contained in:
Mark Qvist 2025-01-06 20:15:33 +01:00
parent 64627c6f8e
commit 675f25520a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/connect.html
View File

@ -11,7 +11,7 @@
<p><center><div class="top_menu lang_menu"><a href="./connect_de.html">Deutsch</a> | <a href="./connect.html">English</a> | <a href="./connect_es.html">Español</a> | <a href="./connect_nl.html">Nederlands</a> | <a href="./connect_pl.html">Polski</a> | <a href="./connect_pt-br.html">Português</a> | <a href="./connect_tr.html">Türkçe</a> | <a href="./connect_jp.html">日本語</a> | <a href="./connect_zh-cn.html">简体中文</a></div><div class="top_menu"><a href="index.html">Reticulum</a> | <a href="start.html">Start</a> | <a href="hardware.html">Hardware</a> | <a href="connect.html">Connect</a> | <a href="docs.html">Manual</a> | <a href="crypto.html">Cryptography</a> | <a href="credits.html">Credits</a> | <a href="https://github.com/markqvist/reticulum">Source</a> | <a href="donate.html">Donate</a></div></center></p>
<h1>Public Testnet</h1>
<p>If you just want to get started experimenting without building any physical networks, you are welcome to join the Public Reticulum Testnet. The testnet is just that, an informal network for testing and experimenting. It will be up most of the time, and anyone can join, but it also means that there's no guarantees for service availability.</p>
<p><strong>Please note!</strong> For everyday use of Reticulum, such as for messaging and other communications, it is much better to use one or more of the community-provided public entrypoints. Please </p>
<p><strong>Please note!</strong> For everyday use of Reticulum, such as for messaging and other communications, it is much better to use one or more of the community-provided public entrypoints. Please see the next section for details. </p>
<p>The testnet runs the very latest version of Reticulum (often even a short while before it is publicly released). Sometimes experimental versions of Reticulum might be deployed to nodes on the testnet, which means strange behaviour can occur. If none of that scares you, you can join the testnet via either TCP or I2P.</p>
<p>Just add one of the following interfaces to your Reticulum configuration file:</p>
<pre><code># TCP/IP interface to the Dublin Hub
@ -38,7 +38,7 @@
<h1>Community-provided Interfaces</h1>
<p>A number of publicly available entrypoints to Reticulum networks have been provided by the community. For everyday use, it is recommended to use these instead of the testnet.</p>
<p>You can connect your devices or instances to one or more of these to gain access to any Reticulum networks they are physically connected to.</p>
<p>Ideally, set up a Reticulum Transport Node that your own devices can reach locally, and then connect that TN to a couple of public entrypoints. This will provide efficient connections and redundancy in case any of them go down.</p>
<p>Ideally, set up a Reticulum Transport Node that your own devices can reach locally, and then connect that transport node to a couple of public entrypoints. This will provide efficient connections and redundancy in case any of them go down.</p>
<pre><code># These are community-provided public Reticulum entrypoints
# served over TCP, and available over the public Internet.

4
source/connect.md
View File

@ -1,7 +1,7 @@
# Public Testnet
If you just want to get started experimenting without building any physical networks, you are welcome to join the Public Reticulum Testnet. The testnet is just that, an informal network for testing and experimenting. It will be up most of the time, and anyone can join, but it also means that there's no guarantees for service availability.
**Please note!** For everyday use of Reticulum, such as for messaging and other communications, it is much better to use one or more of the community-provided public entrypoints. Please
**Please note!** For everyday use of Reticulum, such as for messaging and other communications, it is much better to use one or more of the community-provided public entrypoints. Please see the next section for details.
The testnet runs the very latest version of Reticulum (often even a short while before it is publicly released). Sometimes experimental versions of Reticulum might be deployed to nodes on the testnet, which means strange behaviour can occur. If none of that scares you, you can join the testnet via either TCP or I2P.
@ -36,7 +36,7 @@ A number of publicly available entrypoints to Reticulum networks have been provi
You can connect your devices or instances to one or more of these to gain access to any Reticulum networks they are physically connected to.
Ideally, set up a Reticulum Transport Node that your own devices can reach locally, and then connect that TN to a couple of public entrypoints. This will provide efficient connections and redundancy in case any of them go down.
Ideally, set up a Reticulum Transport Node that your own devices can reach locally, and then connect that transport node to a couple of public entrypoints. This will provide efficient connections and redundancy in case any of them go down.
```
# These are community-provided public Reticulum entrypoints