Git-Mirrors/Reticulum
1
0
Fork 0
mirror of https://github.com/markqvist/Reticulum.git synced 2025-05-02 14:46:05 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated documentation

Browse source
This commit is contained in:
Mark Qvist 2024-06-01 16:32:58 +02:00
parent 30228d12f7
commit 9371f857a8
22 changed files with 85 additions and 58 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/source/gettingstartedfast.rst
View file

@ -244,6 +244,13 @@ Many other Reticulum instances are connecting to this testnet, and you can also
via other entry points if you know them. There is absolutely no control over the network
topography, usage or what types of instances connect. It will also occasionally be used
to test various failure scenarios, and there are no availability or service guarantees.
Expect weird things to happen on this network, as people experiment and try out things.
It probably goes without saying, but *don't use the testnet entry-points as
hardcoded or default interfaces in any applications you ship to users*. When
shipping applications, the best practice is to provide your own default
connectivity solutions, if needed and applicable, or in most cases, simply
leave it up to the user which networks to connect to, and how.
Adding Radio Interfaces