Reading FTRCRP Over Reticulum, audio
Listen to this guide, voiced by Andrew.
Why a second road
The web is one road to this site. It runs through a domain registrar, a hosting provider, a certificate authority and whatever sits between you and them. Most days that is fine. On the day it is not, a mirror that needs none of those things is worth having.
Reticulum is a networking stack built for exactly that. It does not care what carries the packets: an ordinary internet link, a local network, a long-range radio, or several of them at once. Every destination is a cryptographic address, so a page is fetched from a key, not from a name somebody else controls (Reticulum, n.d.).
FTRCRP runs a node on that network. It serves the whole site as plain text pages, rebuilt from the same source as the page you are reading now.
What you will find there
The node carries the security digests, the signals, the investigations and the guides, each in full, in the same order as on the web. No scripts, no images, no tracking, nothing to load from anywhere else. It is the text and the links between the texts.
Our node address:
15e8e28a1679f391d65531416b6f4e46
It announces itself under the name FTRCRP Mint Node.
Install a client
The easiest way to read pages on Reticulum is Nomad Network, a terminal program that is both a browser and a messenger (Qvist, n.d.). On Linux or macOS with Python installed:
pipx install nomadnet
nomadnet
The first start creates an identity and a configuration under your home directory, then opens the interface. If you prefer plain pip, pip install nomadnet works the same way.
Reach the network
Out of the box, Reticulum finds other nodes on your own local network by itself. To reach us from somewhere else you need at least one path into the wider network.
The Reticulum manual is clear about how to do that well: rather than everyone typing in the same handful of public addresses, enable interface discovery and let your node find entry points near you, which keeps the network from collapsing into a few central hubs (Reticulum, 2026). The manual’s getting-started chapter walks through it.
If you only want to try it tonight, adding one public entry point to the [interfaces] section of ~/.reticulum/config is enough. Our node is currently reachable through the bnZ hub in Sweden:
[[bnZ Sweden]]
type = TCPClientInterface
enabled = yes
target_host = node01.rns.bnz.se
target_port = 4242
Restart Nomad Network after editing the file.
Open our node
In Nomad Network, open the Network view. Announced nodes appear in the list as they are heard; give it a few minutes on a first connection. Select FTRCRP Mint Node, or press Ctrl+U and paste the address above, and the index page opens. From there the digests, signals, investigations and guides are one link away. Save the node as a favourite and it stays in your list.
What it does and does not protect
A Reticulum page request is encrypted end to end between you and our node, and the node never learns more about you than the destination you connect from. That is a real improvement on the web.
It is not anonymity by default. The hub you connect through sees the internet address you connect from, the same way any server does. If that matters to you, connect to the hub over Tor or a VPN, or reach the mesh through a local radio link instead of the internet (Reticulum, 2026).
Keeping it current
The mesh copy is regenerated from the site source whenever we publish, so a new digest on the web is a new page on the node shortly after. If the two ever disagree, the web version is the one we stand behind, and we would like to hear about it.
References
Qvist, M. (n.d.) Nomad Network [GitHub]. Available at: https://github.com/markqvist/NomadNet (Accessed: 15 October 2026).
Reticulum (n.d.) Reticulum Network. Available at: https://reticulum.network/ (Accessed: 15 October 2026).
Reticulum (2026) Getting Started Fast, Reticulum Network Stack manual. Available at: https://markqvist.github.io/Reticulum/manual/gettingstartedfast.html (Accessed: 15 October 2026).