diff --git a/docs/connect.html b/docs/connect.html index 5599f5a..9aa9e85 100644 --- a/docs/connect.html +++ b/docs/connect.html @@ -35,7 +35,7 @@ peers = g3br23bvx3lq5uddcsjii74xgmn6y5q325ovrkq2zw2wbzbqgbuq.b32.i2p

The testnet also contains a number of Nomad Network nodes, and LXMF propagation nodes.

-

Community-provided Interfaces

+

Community Entrypoints

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.

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 transport node to a couple of public entrypoints. This will provide efficient connections and redundancy in case any of them go down.

diff --git a/source/connect.md b/source/connect.md index 94e6d71..f162bb4 100644 --- a/source/connect.md +++ b/source/connect.md @@ -31,7 +31,7 @@ Just add one of the following interfaces to your Reticulum configuration file: The testnet also contains a number of [Nomad Network](https://github.com/markqvist/nomadnet) nodes, and [LXMF](https://github.com/markqvist/lxmf) propagation nodes. -# Community-provided Interfaces +# Community Entrypoints 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. 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.