Skip to content

gorrcd — RRC Hub Daemon

gorrcd is a standalone, high-performance Reticulum Relay Chat (RRC) hub daemon written in 100% Go. It serves chat rooms over the Reticulum network, provides channel history persistence, and is 100% wire-compatible with Python rrcd and NomadNet clients.


Key Features

  • High Concurrency: Handles dozens of simultaneous connected clients and high message volumes with minimal memory and CPU usage.
  • Persistent Channels: Retains room message histories across hub restarts.
  • Key-Protected Rooms (+k): Supports encrypted rooms accessible only to clients with the shared channel key.
  • Direct Notice Delivery (K_DST): Routes private notices directly between connected clients on the hub.
  • Private Commands (CAP_PRIVATE_COMMAND): Accepts a command line addressed to the hub's own identity from a client that has not joined a room, and lets a user send a direct message to another participant by nickname. Stock Python rrcd has no private-message command; the capability is advertised only when enabled and is ignored by hubs and clients that do not know it.
  • Message of the Day (MOTD): Configurable announcements broadcast to users when joining rooms.

Quickstart

Run gorrcd for the first time:

gorrcd

On first run, gorrcd writes ~/.rrcd/rrcd.toml and ~/.rrcd/rooms.toml, generates its hub identity at ~/.rrcd/hub_identity, and exits cleanly.


Configuration (~/.rrcd/rrcd.toml)

~/.rrcd is the default home; set RRCD_HOME to keep it elsewhere.

[hub]

# Optional: Reticulum configuration directory. Unset means Reticulum's own
# default, usually ~/.reticulum.
configdir = ""

# The hub's persistent identity.
identity_path = "~/.rrcd/hub_identity"

# Registered rooms, topics, modes and bans. gorrcd maintains this file, and a
# running hub re-reads it with /reload.
room_registry_path = "~/.rrcd/rooms.toml"

# The name clients show beside the hub's version, and the greeting they see.
hub_name = "gorrcd"
greeting = ""

# Announce once at startup, and how often after that (0 = startup only).
announce_on_start = true
announce_period_s = 0.0

# Accept private command lines addressed to the hub and advertise
# CAP_PRIVATE_COMMAND in the WELCOME. The default is true; set false for a
# WELCOME byte-identical to stock Python rrcd.
enable_private_commands = true

# Name the joiner in JOINED notifications. A bot already in a room needs this to
# learn about peers that join later, and to answer them.
include_joined_member_list = false

Rooms live in ~/.rrcd/rooms.toml, not in rrcd.toml:

[rooms."general"]
topic = "Public discussion"

[rooms."operations"]
topic = "Operations team only"
moderated = true
operators = ["<identity hash>"]

Each room takes founder, topic, moderated, operators, voiced, bans and invited; every identity is a hex hash. A key-protected room (+k) is set from the client, not from this file.


Private Messages Between RRC Users

RRC itself has no private-message command. gorrcd adds one without changing the protocol: when enable_private_commands = true (the default) the hub advertises the capability CAP_PRIVATE_COMMAND (K_CAPS key 3) in its WELCOME, and a NOTICE whose K_DST is the hub's own identity hash — the hash the WELCOME came from, not the hub's destination hash — is read as a command line and answered on that client's link alone.

Unknown capability keys are ignored by stock rrcd and by RRC clients, so no Python hub or Python client needs any change, and a client only ever sends one of these commands to a hub that advertises the key.

Command Aliases Effect
/dnotice <nick\|hash\|me> <text> /dn, /msg One direct notice to that participant alone.
/dnoticeme <text> — One direct notice to the sender's own link.
/dnoticecap — Reports whether the hub advertises the capability.

Targets resolve exactly — a full identity hash, a hex prefix of at least six characters, or a nickname — and a token that matches more than one participant is reported with nothing sent. There is no fuzzy matching. A nickname containing spaces must be quoted: /msg 'gonomadnet on MiniPC' yo dude. The hub confirms delivery to the sender with the recipient's full hash and the message id, or reports not found, the ambiguity list, or that the body does not fit the target's link.

See Protocol & Markup Extensions for the envelope layout, hub processing rules, and a Python back-port guide, and the go-reticulum README for the client-side behaviour in gonomadnet.


Interoperability

gorrcd is drop-in compatible with: - NomadNet (Python and Go versions) - gorrcbot (Go RRC bot) - Official Python rrcd clients and hubs