Simple RNS page publisher

Back

If you’re looking for a dead simple way to publish pages on RNS, then reticulum-go has you covered. Installing packages with Python is not rocket science but it’s not that convenient either.

As of August 2026, the latest release of reticulum-go is v1.0.1. The project supports all mainstream OSes (linux, macOS, windoze). A standalone page server¹ is provided in the release. It’s around 11MB in size.

Here are the commands I used to get it running locally. If you download binaries more frequently, then consider checking the digest also² for safety purposes. We’ll recklessly skip that now for the sake of simplicity.

# download the binary
wget https://github.com/Quad4-Software/Reticulum-Go/releases/download/v1.0.1/reticulum-go-example-pageserver-linux-amd64 -o rpp

# make the binary executable
chmod +x rpp

# run the binary
./rpp

Please note, I’m running a linux system, so I chose the linux-amd64 binary. You’ll have to scan the release listing to find the correct binary and URL for your system³. I also rename the binary to “rpp” but feel free to use whatever you like (and will remember 🙃).

The binary automatically creates a pages/ and files/ directory wherever you run it. You can fire up your favourite $EDITOR and start writing your pages in a fresh pages/index.mu.

Check ./rpp -h for all the CLI options. Some useful options include:

Turn down the verbose logging with -log-level 2 (only warnings and errors)
Increase the announce interval with -a 1 (every minute when testing)
Specify the name of your node with -node-name <name> (the name others will see)
Configure when the pages are reloaded with -page-refresh 10 (every 10 seconds while hacking)

The default configuration is found in ~/.reticulum-go/config. You can add your interfaces there.

reticulum-go will not re-use any existing RNS identity and will generate it’s own data in ~/.reticulum-go. So, your existing RNS data in ~/.reticulum will not be clobbered.

You typically can’t run the page server on the same system your run nomadnet or rns without running into a port conflict. This can be configured (see ~/.reticulum-go/config) but it’s handiest to run the page server somewhere where you don’t run other RNS programs.

The documentation for the page server itself is pretty good, I recommend reading that README.md if you get stuck or lost.

If you wished the binary was even smaller for transferring it to remote devices, then I can recommend using upx. When I run the following command, I can get the binary down to around 3.6MB. This will make the binary slower to start up (because it needs to unpack itself) but I generally don’t notice the speed difference myself.

upx --best --lzma ./rpp

Happy Hacking ✌️

Besides the standalone binary, you can run the full RNS stack in Go. You can download the full RNS binary from the release listing (it’s around 12MB) and follow roughly the same set of steps as this short guide shows. The page server is also provided with the fully binary but as a sub-command, e.g. you would run ./reticulum-go pageserver. I believe the separate binary for the page server is provided for the convenience of people who only want to publish pages.↩︎
On the release listing, you see a whole bunch of digests listed above the binaries. If you run sha256sum ./rpp then you will generate a digest locally on your machine. Compare this digest with the one written on the release listing. If they match, then you know what you got in the binary is what the developer intended to release and it isn’t malware.↩︎
It’s pretty confusing but very roughly: darwin is macOS, amd is used for a lot linux systems and arm is usually a raspberry pi, or small devices. Your favourite search engine will help you out further. If you see a weird error when you try to run the page server, then you probably chose wrong. Once you know, “you know”, this architecture naming stuff doesn’t change that often at all.↩︎