Mirror/Reticulum
1
0
Fork 0
mirror of https://github.com/markqvist/Reticulum.git synced 2026-07-03 07:13:59 -07:00
Code Issues Packages Projects Releases Wiki Activity

Added markdown manual build

Browse Source
This commit is contained in:
Mark Qvist
2026-05-06 21:18:01 +02:00
parent 4d6e164d62
commit ec27d8bfde
18 changed files with 1025 additions and 166 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/markdown/gettingstartedfast.md
+1 -7
View File
@@ -117,8 +117,6 @@ start with reading the next section, [Bootstrapping Connectivity](#bootstrapping
as this provides the most essential understanding of how to ensure reliable
connectivity with a minimum of maintenance.
<a id="bootstrapping-connectivity"></a>
## Bootstrapping Connectivity
Reticulum is not a service you subscribe to, nor is it a single global network you “join”. It is a *networking stack*; a toolkit for building communications systems that align with your specific values, requirements, and operational environment. The way you choose to connect to other Reticulum peers is entirely your own choice.
@@ -186,8 +184,6 @@ A global, distributed backbone of Reticulum Transport Nodes is being run by volu
As a good starting point, you can find interface definitions for connecting your own networks to this backbone on websites such as [directory.rns.recipes](https://directory.rns.recipes/) and [rmap.world](https://rmap.world/).
<a id="hosting-entrypoints"></a>
## Hosting Public Entrypoints
If you want to help build a strong global interconnection backbone, you can host a public (or private) entry-point to a Reticulum network over the
@@ -339,8 +335,6 @@ The entire Reticulum API is documented in the [API Reference](reference.md#api-m
chapter of this manual. Before diving in, it’s probably a good idea to read
this manual in full, but at least start with the [Understanding Reticulum](understanding.md#understanding-main) chapter.
<a id="install-guides"></a>
## Platform-Specific Install Notes
Some platforms require a slightly different installation procedure, or have
@@ -687,4 +681,4 @@ No matter how Reticulum is installed and started, it will load external dependen
only if they are *needed* and *available*. If for example you want to use Reticulum
on a system that cannot support `pyserial`, it is perfectly possible to do so using
the rnspure package, but Reticulum will not be able to use serial-based interfaces.
All other available modules will still be loaded when needed.
All other available modules will still be loaded when needed.