T383838gorrcbot is a headless, always-on RRC (Reticulum Relay Chat) bot and autonomous off-grid assistant. It operates as a client, not a hub: it connects to one or more RRC hubs simultaneously, joins configured rooms, maintains connectivity across link drops, and serves requests addressed to its nick or cryptographic identity hash.

• A Thin CLI Over a Shared Engine: The sensors, the geodetic maths, the

field tools, the command registry, and the captive portal all live in the

library package

github.com/gmlewis/go-reticulum/bot,

where grl — the Go Reticulum Lifesaver appliance — runs the very

same code in-process. T383838cmd/gorrcbot is only the command line and the

Reticulum wiring, so a radio reply and a dashboard answer can never drift

apart, and T383838bot.Engine.Eval evaluates a command with zero hops and zero

airtime.

• Single Identity Everywhere: T383838gorrcbot generates one 64-byte Reticulum private identity (T383838bot_identity) and uses it across all connected hubs. Its identity hash is identical on all hubs, allowing users to reach it using consistent address prefixes.

• Strict Addressing Contract: The bot is completely silent unless addressed directly. It will never spam channels, and it completely ignores chat traffic not directed at it.

• Rate-Limiting & Cooldowns: Built-in per-identity cooldown prevents abuse or channel flooding over low-bandwidth LoRa links.

• Offline First: The vast majority of tactical and field assistant commands (Plus Codes, geodesy, dead reckoning, sun/moon ephemeris, wilderness medicine cards, Morse code, unit conversions, and the cell/repeater finder with its built-in WGS-84 ↔ GCJ-02 conversion) compute entirely in-process with zero internet connection required. The marine, aviation, navigation, and communications-site catalogs are embedded too, so T383838search, T383838near, and T383838list find a station id before any provider is configured and while a provider is unreachable.

• Low-Bandwidth by Design: Long answers are paginated to the operator's T383838max_reply_lines budget, every page carries the exact command that asks for the next one, and T383838more / T383838next continue a walk through a catalog without retyping the query.

• Graceful Telemetry Degradation: For commands that query external live telemetry (weather, marine tides, buoys, river gauges, flight tracking, space weather), providers are queried through sanitized HTTP/HTTPS templates. If an endpoint is unconfigured or unreachable, the bot reports honest failure without guessing or hallucinating.

Run T383838gorrcbot without arguments:

T282828

On its very first invocation, T383838gorrcbot:

1. Creates the storage directory T383838~/.gorrcbot/storage/.

2. Generates a fresh 64-byte private key file T383838~/.gorrcbot/bot_identity with restrictive permissions (T3838380600).

3. Writes a fully documented, pre-populated default configuration file to T383838~/.gorrcbot/config.toml.

4. Prints a notice and exits cleanly with code T3838380, allowing you to review and configure hubs before establishing network connections.

Perform a dry-run check without connecting to any hubs:

T282828

T282828

Use T383838--log-level DEBUG or T383838--log-file /var/log/gorrcbot.log as desired.

Here is the complete configuration format with verified, working default providers:

T282828

The bot answers when addressed in any of the following manners:

166

| Method | Example | Behavior |

|--------|---------|----------|

| Room message with nick prefix | T383838@gobot help | Works in any room where the bot is present. Tolerates T383838: or T383838, suffix (T383838@gobot: ping). |

| Room message with hash prefix | T383838@a012129c help | Addressed by the first 6+ hex characters of the bot's identity hash. |

| Direct Notice (T383838K_DST) | T383838/notice @gobot help or T383838/msg gobot help | Direct notices do not require typing T383838@gobot. The bot replies directly back to the sender. |

While T383838@gobot can be triggered publicly inside any room it has joined, private direct messaging is strongly recommended for most commands:

T282828

exchange without a chat client — it joins the hub, sends one T383838/msg gobot ...

line, prints the reply to stdout, and exits. Its hub destination is hard-coded

to the official gonomadnet Public RRC Hub, so T383838gobot help reaches the

official T383838@gobot out of the box.

From a shell: the gobot CLI performs exactly this

exchange without a chat client — it joins the hub, sends one T383838/msg gobot ...

line, prints the reply to stdout, and exits. Its hub destination is hard-coded

to the official gonomadnet Public RRC Hub, so T383838gobot help reaches the

official T383838@gobot out of the box.

1. Bandwidth Preservation on LoRa & Radio Meshes:

Reticulum channels often operate over bandwidth-constrained radio networks (such as LoRa at 1–5 kbps or VHF packet radio). Commands with verbose or multi-line responses (such as T383838help, T383838metar, T383838sun, T383838weather, T383838tide, T383838loc, T383838buoy, or T383838kjv) take several seconds to transmit. Running them privately keeps shared room airtime clear for human peer conversation.

2. Operational Security (OPSEC) & Coordinate Privacy:

Commands such as T383838loc, T383838proj, T383838dist, T383838sun, T383838weather, and especially T383838checkin or T383838sitrep involve exact geographic coordinates, personal waypoints, or overdue travel timelines. Querying privately ensures that your physical location and itinerary are not broadcast to every listener on a public hub.

3. Channel Courtesy:

Queries for space weather (T383838spacewx), flight tracking (T383838flight), marine buoys (T383838buoy), or unit conversions (T383838conv) generate chatter that may distract or interrupt other room participants.

• Addressing Flexibility: In RRC, T383838/msg gobot <command> (or T383838/dnotice gobot <command>) packages the message into a direct notice envelope with T383838K_DST set directly to the bot's 16-byte identity hash. Because the envelope itself addresses the bot, the trigger prefix is optional:

• T383838/msg gobot help

• T383838/msg gobot @gobot help

Both work identically.

• Strict Private Reply Guarantee: When a request arrives via direct notice (T383838K_DST), T383838gorrcbot's reply routing policy always transmits the response as a direct notice back to the sender's cryptographic identity hash (T383838msg.Src). The response never leaks or appears in any public room.

• Direct Notice Capabilities (T383838CAP_DIRECT_NOTICE): Direct messaging requires that the connected hub supports RRC direct notice routing (T383838CAP_DIRECT_NOTICE = 2), which all modern T383838rrcd and T383838gorrcd hubs provide. If a hub cannot deliver direct notices, T383838gorrcbot safely drops the direct reply rather than leaking it into a public channel.

Three of the field assistant's commands are useless without an identifier: T383838tide

takes a 7-digit NOAA station id, T383838buoy takes a 4–8 character NDBC station id,

and T383838metar takes a 4-letter ICAO code. None of them can be guessed. Rather than

leave an operator to find one on another device, every one of those catalogs is

embedded in the binary and searched offline:

312

| Form | What it does | Example |

|------|--------------|---------|

| T383838<cmd> search <query> [page] | Case-insensitive match on the identifier, the name, the state or region, and (for T383838metar) the city and IATA code. Every word of the query must appear somewhere in the row. | T383838@gobot tide search san francisco |

| T383838<cmd> near <place|coords|pluscode> | The three rows closest to a position, nearest first, with the distance in nautical miles and the compass bearing. The argument may be a position in any of the five notations, a Plus Code, or a name or identifier from the catalog itself. | T383838@gobot buoy near 37.8,-122.4 |

| T383838<cmd> list [state|region] [page] | Every row, or only those in a state (T383838CA, T383838OR, T383838WA), a state's own name (T383838california), or a basin or country code (T383838GOM, T383838ATL, T383838CAR, T383838GB). | T383838@gobot metar list CO |

The catalogs are data, not guesses, and they are read without touching the

network — which is the point. A station id is discoverable before the

operator has configured T383838tide_url, T383838buoy_url, or T383838metar_url, and while that

provider is unreachable:

T282828

Once an id is known, the original form is unchanged and answers with live

telemetry: T383838@gobot tide 9414290, T383838@gobot buoy 46026, T383838@gobot metar KDEN.

353

| Command | Catalog | Size | Region codes |

|---------|---------|------|--------------|

| T383838tide | Every NOAA CO-OPS tide-prediction station the provider publishes | ~3,500 stations | US state codes, plus T383838PR, T383838VI, T383838GU, T383838AS, T383838MP |

| T383838buoy | Every NDBC station that reports meteorological data, worldwide: Pacific, Atlantic, Gulf, Caribbean, Hawaii, Alaska, and the Great Lakes | ~900 stations | US state codes, plus T383838ATL, T383838GOM, T383838CAR, T383838PAC |

| T383838metar | Every OurAirports field with an IATA code and scheduled service, worldwide | ~5,100 airfields | US state codes, plus two-letter country codes (T383838GB, T383838FR, T383838JP, …) |

| T383838tower | Hand-maintained mountain-top and regional communications sites: amateur repeaters, cellular masts, public-safety relays, and marine VHF stations, balanced between the United States and China with major international hubs | ~220 sites | US state codes, Chinese province codes (T383838BJ, T383838GD, T383838SC, T383838XJ, …), and country codes (T383838US, T383838CN, T383838GB, T383838JP, …) |

The T383838tide, T383838buoy, and T383838metar tables are the providers' catalogs in full,

not a selection: a station is carried because it meets the filter in its file's

header, so T383838near answers with the genuinely nearest station anywhere on earth

and T383838search / T383838list page through the rest. Only T383838tower is assembled by

hand, because no public feed publishes a comparable site list.

They are refreshed from the live public sources by

update-offline-data, which rewrites a table only

when upstream differs and then reports it up to date. The T383838tower table is

the one dataset the tool does not touch.

A T383838metar region may be a state code or a country code, and the two can

collide (T383838CO is both Colorado and Colombia). A state always wins: `metar

list COT383838lists Colorado, and Colombia's fields are reached by name —metar

list colombiaT383838. The same rule applies to ART383838, CAT383838, DET383838, IDT383838, INT383838, MA`,

and T383838TN. Every country code that does not collide works unchanged.

A station id that is not in a catalog is still accepted by its command,

because each provider is authoritative about its own stations; the embedded

catalog is a shortcut for finding the right one, not a filter on what may be

asked.

A catalog answer is deliberately bite-sized. On a 1–5 kbps LoRa link a long

reply is not merely slow, it is truncated: the reply policy emits one NOTICE

per line and cuts anything past T383838max_reply_lines. A page is therefore sized from

that same budget:

• Page size follows the budget. The bot reserves two of the T383838max_reply_lines

lines for the header and the footer, and puts at most four rows on a page

(T383838max_reply_lines = 12 → 4 rows; T383838max_reply_lines = 4 → 2 rows;

T383838max_reply_lines = 3 → 1 row). Raising the budget widens every page with no

command change.

• Every page says where it is. The first line names the query and the

position — T383838Tide stations in CA (Page 1 of 3):.

• Every page says how to continue. The last line carries the exact command

for the next page, and the T383838more shortcut:

T383838[Page 1 of 3: ask "tide list CA 2" or "more" for next]. The last page ends

with T383838[Page 3 of 3: end of results].

• Pages are explicit and repeatable. T383838<cmd> search <query> 2 and

T383838<cmd> list CA 2 reach page 2 directly, so a page can be quoted, shared, and

re-read. A page past the end answers T383838page 9 not found (total 3 pages)

instead of an empty reply.

For a one-to-one private session, T383838/msg gobot more (or T383838/msg gobot next)

answers the page after the one just sent, with no need to retype the query:

T282828

• The pending page is remembered per identity, in memory only, for **five

minutes** and for at most 256 requesters. Nothing is written to disk, a restart

forgets every pager, and one asker's page is never handed to another.

• The cache holds the command for the next page, not the page itself, so a

walk through a hundred rows costs a few bytes per asker and every page is

rendered with its own correct footer.

• With nothing pending, or after the timeout, the answer is

T383838no more pages or search expired.

• T383838more and T383838next are exempt from the per-identity cooldown, because a page

turn answers a page the asker was just told to ask for and can only produce

offline catalog rows. Every other command keeps its cooldown.

A NomadNet client renders Micron markup, so the bot can offer the same pages as

buttons instead of as commands to retype. Set T383838micron_links = true in

T383838config.toml to render each row as a link to the command that fetches it, and

the footer as a Next Page link:

T282828

The option is off by default: an RRC NOTICE is plain text to every reader

except a NomadNet one, and a link that is not rendered is just noise. The links

address the nick the bot really answers to, so they work as written in the room

they were sent to.

T383838tower answers the question that decides whether an off-grid party can

communicate at all: what transmits near here, which way is it, and how far?

The catalog, the geometry, and the coordinate conversion are all embedded in the

binary, so the answer is available with no network connection of any kind.

1. Aiming a directional antenna. With a weak or unusable signal on a

rubber-duck antenna, a Yagi, log-periodic, or grid antenna pointed at the

right mast can hold an emergency uplink. What the operator needs is not a map

but a bearing and a distance — which is exactly what T383838tower near prints.

2. Choosing a direction to walk. A stranded driver or hiker who has lost

coverage needs to know which way regains it, and how far the walk is.

3. Amateur radio when the cellular network is gone. Mountain-top VHF/UHF

repeaters are frequently solar- and battery-backed and survive the event that

took the commercial network down — but only if the operator knows the

frequency, the offset, and the CTCSS/PL tone.

4. Public safety and marine channels. Search-and-rescue relays and coastal

marine VHF stations are in the same catalog, so the same query reaches the

people whose job the emergency is.

T282828

T383838repeater, T383838cell, and T383838mast are aliases for T383838tower and behave identically.

A proximity answer names the three closest sites, with the distance, the bearing

and compass point, the service, and the radio details needed to use the site:

T282828

With a live compass heading and no typed argument, each row adds the **relative

steering instruction** that aims an antenna at the site without arithmetic — see

Radio direction finding:

T282828

Search and list are offline lookups over the whole catalog, and both paginate to

the reply budget:

T282828

T383838tower info renders one site in full — both datums, the Maidenhead grid an

operator signs with, the elevation, and every radio detail:

T282828

The catalog is deliberately balanced between the United States and China, with a

selection of major international hubs, because the same tool has to be as useful

on the Sichuan–Tibet highway as it is on a Colorado fourteener. Chinese entries

carry province codes and pinyin place names, so an operator who thinks in

English and an operator who knows the two-letter code both reach the same rows:

T282828

WGS-84 ↔ GCJ-02 ("Mars coordinates") conversion. China mandates that

domestic maps publish coordinates in GCJ-02, which is GPS with a deliberately

non-linear offset of several hundred meters. A coordinate copied out of Amap,

Gaode, Tencent Maps, or WeChat and fed to a GPS receiver lands in the wrong

street, and a GPS coordinate dropped into Amap lands several hundred meters

away. The bot handles both directions:

• A site inside China prints its GCJ-02 coordinate alongside the WGS-84 one,

ready to paste into a Chinese map app:

T282828

• A GCJ-02 coordinate is handed back to the bot with a T383838gcj: (or T383838gcj02:)

prefix, anywhere a location is accepted, and is converted to the GPS position

behind it first. Nothing outside China is ever moved: the conversion is

applied only inside the mandated bounding box, so every foreign coordinate

round-trips bit-for-bit.

T282828

The inverse transform is recovered by fixed-point refinement of the published

forward equations, converging to better than a centimeter.

T383838tower list accepts a region code (T383838CA, T383838CO, T383838BJ, T383838GD, T383838SC, T383838XJ), a US

state's name (T383838california), a country code (T383838US, T383838CN, T383838GB, T383838JP), or a

country's name (T383838china, T383838germany, T383838canada).

A two-letter code that is a US state names the state, so T383838tower list CA

is California rather than Canada, and T383838tower list DE is Delaware rather than

Germany — those countries are reached by name (T383838tower list canada,

T383838tower list germany). A Chinese province that shares a US state's code is

still listed beside it, because the region itself matches: T383838tower list SC

covers South Carolina and Sichuan, and T383838tower list SD, T383838NM, and T383838HI

similarly cover both countries' regions of that name.

The embedded tower list is a planning reference, not a live directory. An operator

who needs micro-cell density — for example an OpenCelliD extract reduced to the

area of operations — drops a CSV at the path configured as T383838towers_path

(by default T383838towers.csv beside T383838config.toml) and every query sees it:

T282828

• The column order is fixed: T383838id,name,type,lat,lng,freq,offset,tone,operator,city,region,country,elev.

• T383838type is T383838RPT, T383838CELL, T383838EMERG, or T383838MAR (the words T383838repeater, T383838cellular,

T383838emergency, and T383838maritime are accepted too).

• T383838lat and T383838lng are WGS-84 decimal degrees; the GCJ-02 conversion is

applied on display.

• A row whose T383838id matches an embedded one replaces it, so a corrected

frequency is corrected everywhere at once; a new T383838id is added.

• The header line is optional, T383838# comments are ignored, and a malformed row is

skipped with a log line naming it rather than silently shortening the file.

• An absent file is normal, and an unreadable one degrades to the embedded

catalog: a bad export can never cost the tool its built-in data.

Nothing in a T383838tower query touches the network. There is no provider URL for

this command and no configuration it needs: the catalog is compiled into the

binary, the distance, bearing, and datum arithmetic are closed form, and the

only file it ever reads is an optional local dataset. It is the one discovery

command that is fully useful before its operator has configured anything at all.

The Go Reticulum Lifesaver (GRL) is the role T383838gorrcbot plays on a

pocket-sized, off-grid survival communicator: a device that replaces a

$300–$600 commercial satellite messenger and its monthly subscription with an

inexpensive, open-source node that works when every link has already failed.

!!! tip "The appliance itself is T383838grl"

This section describes the survival intelligence T383838gorrcbot shares with the

appliance. To run the whole appliance — Reticulum, the GNSS receiver and

compass, the zero-hop field assistant, and the captive dashboard the phone

reads — use grl, which mounts the very same

bot engine

in-process.

It obeys one rule above all others, the Autonomous Local Intelligence Rule:

nearby masts, the sun, and "where am I?" answer in microseconds with **0 radio

hops, 0 airtime, and 0 RF emissions**.

Survival intelligence must run locally, in-process. Emergency medicine,

nearby masts, the sun, and "where am I?" answer in microseconds with **0 radio

hops, 0 airtime, and 0 RF emissions**.

Everything in this section therefore works with the radio switched off, with no

internet, and with no account.

T383838gorrcbot speaks NMEA-0183 directly, with no Cgo driver and no third-party

library. It reads T383838$GNRMC / T383838$GPRMC (position, time, date, validity, speed,

course) and T383838$GNGGA / T383838$GPGGA (fix quality, satellites, HDOP, altitude,

geoidal separation), validates the XOR checksum of every sentence byte-for-byte,

and merges the rotation of sentences a receiver emits into one live fix. A

sentence that fails validation is dropped silently: a corrupted sentence is a

wrong position, and a wrong position is worse than no position at all.

Two T383838[bot] keys configure the source:

T282828

With neither key set, the node simply has no position, and every command that

would use one says so instead of guessing. With T383838gps_port set, the sentences

are parsed in the background as they arrive; with T383838gps_fix, the position is

constant and no device is opened.

Every position-aware command shares one receiver, so the radio reply and the

web dashboard can never disagree about where the device is.

A GNSS receiver has one blind spot that matters most exactly when it hurts: it

derives course over ground from motion, so an operator who is standing

still — injured, pinned down by weather, lost in fog, or aiming a Yagi at a

mountain-top repeater — has no heading at all. The receiver reports the last

course it saw, noise, or nothing.

Pairing the node with an inexpensive 3-axis magnetometer (a QMC5883L or an

LSM303 on I2C, behind any serial bridge) removes that blind spot. T383838gorrcbot

reads the standard marine/electronic heading sentences directly, with the same

pure-Go NMEA parser and the same byte-for-byte XOR checksum validation it uses

for the receiver:

129

| Sentence | Carries | Example |

|----------|---------|---------|

| T383838$HCHDG | Magnetic heading, deviation, and variation | T383838$HCHDG,101.1,,,13.1,E*1B → 101.1° magnetic, +13.1° east → 114.2° true |

| T383838$HCHDM | Magnetic heading only | T383838$HCHDM,101.1,M*28 |

| T383838$HCHDT | True heading only | T383838$HCHDT,114.2,T*2F |

A sentence that fails its checksum is dropped in silence, because a corrupted

heading is a wrong direction, and a wrong direction is worse than none.

T282828

With neither key set, the node simply has no heading, and every answer that

would use one says so instead of guessing. With T383838compass_port set, the

sentences are parsed in the background as they arrive; with T383838compass_heading,

the bearing is constant and no device is opened.

True north, automatically. A magnetic compass points at magnetic north,

which is not the north a map, a bearing, or a rescue grid uses — the difference

ranges from a fraction of a degree to more than twenty depending on where the

operator stands, and thirteen degrees of error at fourteen kilometers is more

than three kilometers of error. T383838gorrcbot therefore converts every magnetic

heading to true north with the World Magnetic Model (WMM2025), evaluated in

pure Go from the published spherical-harmonic coefficient table: no data files,

no network, no third-party library. The model reproduces its own published test

vectors to the precision they are printed at, and its declination is checked

against the reference values for San Francisco, Denver, Boston, London, and

Tokyo.

Three sources of variation are used in that order of preference:

1. The variation field of the sentence itself (T383838$HCHDG), which the

instrument measured where it stands.

2. The World Magnetic Model at the node's live GNSS fix, which is what

turns a T383838$HCHDM magnetic heading into a true one with no operator input.

3. Nothing at all, when the node has neither — in which case the heading is

reported as magnetic and labelled as such everywhere, never passed off as

true north.

T383838whereami (also typed T383838/whereami) prints the card an operator reads before

moving, assembled entirely from the in-tree geodetic engines:

T282828

The Heading / Course line appears only when the device actually has a

heading, and only on the card about the device's own position — a heading

describes which way the operator is facing, so printing it beside a remote

coordinate would invite the reader to think the two belong together. The line

never claims more than it knows:

| State | Line |

|-------|------|

| Variation known (sentence or WMM) | T383838042° True (029° Mag, Var: +13.0° E) · NE |

| True only (T383838$HCHDT) | T383838042° True · NE |

| Magnetic only (no position) | T383838029° Mag · NNE |

| No compass at all | the line is omitted cleanly; the card is unchanged |

Every notation is there because somebody else needs it: a Plus Code is what a

dispatcher can paste into a map, a Maidenhead square is what an amateur operator

logs, decimal degrees are what a GPS unit takes, and — inside China — the

GCJ-02 pair is the only form Amap, Gaode, Tencent Maps, and WeChat accept, so

the card adds that line for a position in China.

170

| Form | Example | Notes |

|------|---------|-------|

| No argument | T383838@gobot whereami | Uses the live GNSS fix, or reports that it is acquiring one. |

| Coordinates | T383838@gobot whereami 37.7553,-122.4527 | Places a remote position; the card says T383838manual position and shows no altitude, because no receiver reported one. |

| Plus Code | T383838@gobot whereami 849VQG4W+4W | Any notation T383838loc accepts works. |

| Maidenhead grid | T383838@gobot whereami CM87ss | The square's own center. |

The eleven-character high-precision Plus Code (about 3 m by 3 m) is computed

alongside the ten-character code and is carried by the dashboard's JSON API

rather than printed on the card.

The local solar time is the zone the position's own longitude defines —

T383838round(longitude / 15) hours — because a node with no timezone database cannot

honestly claim to know an operator's civil zone or whether summer time is in

force. Solar noon and the sunset countdown are computed against that same clock,

for the operator's local calendar day.

A person with cold hands, in the dark, does not want to type coordinates. When a

GNSS fix is live, the field commands inherit it automatically:

236

| Command | With a fix | Without a fix |

|---------|-----------|---------------|

| T383838tower near | The three closest masts and repeaters to the operator's own position — and, with a live compass heading, the relative turn that aims an antenna at each one. | Asks for T383838<place|coords|pluscode>. |

| T383838cell near, T383838repeater near, T383838mast near | Same, for one service. | Same. |

| T383838tide near | The three closest tide stations, offline. | Asks for a location. |

| T383838sun | The almanac at the current position; T383838sun 2026-06-21 keeps the date and takes the position from the fix. | Asks for a location. |

| T383838sos | Raises a RED beacon at the verified position. | Asks for T383838<loc> <TRIAGE> <details>. |

| T383838sos RED two hikers, one leg fracture | Raises the beacon at the fix with the triage and details given. | Same as above. |

A beacon raised from the fix attaches the receiver facts to the record and to

the reply — satellites, HDOP, altitude, fix quality, and the receiver's own

timestamp — so a rescue party reading the registry after the link has failed

knows not just where the beacon is but **how much the position can be

trusted**:

T282828

A typed location always wins: T383838sos 39.7392,-104.9903 RED climber hurt stays

about the climber in Denver, never about the device's own position. And with no

fix at all, the automatic fallback never fires, so a mistyped request can never

become a beacon somewhere arbitrary.

A bearing is a fact; a turn is an instruction. With a live heading, a

zero-argument T383838tower near stops printing a bearing to interpret and starts

printing the turn to make:

T282828

The instruction is a real clock face — **twelve straight ahead, three to the

right, six behind, nine to the left** — so it can be acted on in the dark

without arithmetic:

| Relative bearing | Instruction |

|------------------|-------------|

| within ±5° | T383838[Ahead · 12 o'clock] |

| +5° to +165° | T383838[Turn X° RIGHT · N o'clock] |

| −165° to −5° | T383838[Turn X° LEFT · N o'clock] |

| beyond ±165° | T383838[Behind · 6 o'clock] |

The steering appears only when it is meaningful, which is a deliberately narrow

condition: the answer must be about the device's own position (a live or

static fix, no typed argument) and the heading must be true, never magnetic.

A target bearing is a true bearing, so steering against an uncorrected magnetic

heading would send the operator off by the local variation. A named place, or a

node with no compass, gets exactly the distance-and-bearing answer it always

got.

Set one key and the device serves a survival dashboard to any phone that joins

its Wi-Fi:

T282828

Nothing is installed, because the page is the binary: one self-contained

HTML document with inline CSS and JavaScript and zero external references —

no stylesheet, font, image, or script from a network. A traveler's phone in

airplane mode opens it with the browser it already has.

The portal answers the captive-network probes the operating systems use, so the

phone's native captive browser opens the dashboard by itself instead of

reporting "connected, no internet":

| Probe | Operating system |

|-------|------------------|

| T383838/hotspot-detect.html | Apple iOS and macOS |

| T383838/generate_204, T383838/gen_204 | Android |

| T383838/ncsi.txt, T383838/connecttest.txt | Windows |

Each probe is answered with a T383838302 redirect to T383838/ and `Cache-Control:

no-store`.

442

| Endpoint | Method | Purpose |

|----------|--------|---------|

| T383838/ | T383838GET | The dashboard: the large Plus Code with a Copy Plus Code button, coordinates, grid, elevation, fix status, the local solar clock, the sunset countdown, the live compass rose, the red SOS button (with a confirmation dialog), and the field-assistant chat box. |

| T383838/api/whereami | T383838GET | The current fix and its full geodetic synthesis as JSON: both Plus Codes, the grid, the coordinates, altitude, speed, course, satellites, HDOP, fix quality, the local solar clock, the sunset, the GCJ-02 pair inside China, the live heading, and the card's own lines. |

| T383838/api/compass | T383838GET | The live compass reading as JSON, with the nearest communications site the rose vectors toward: T383838{"valid": true, "mag_deg": 29, "true_deg": 42, "declination_deg": 13, "cardinal": "NE", "target": {"kind": "site", "id": "W6PW-2M", "name": "Sutro Tower", "bearing_deg": 144.4, "distance_km": 0.0, "steering": "[Turn 102° RIGHT · 3 o'clock]"}}. It answers even with no GNSS fix, because a compass works standing still. |

| T383838/api/query | T383838POST | Runs one local command and returns its reply lines: T383838{"command": "med hypothermia"} → T383838{"command": "med hypothermia", "lines": ["[HYPOTHERMIA] …"]}. An addressed nick and a leading slash are both accepted, so T383838@gobot med hypothermia, T383838/med hypothermia, and T383838med hypothermia are the same request. |

The dashboard carries a north-up compass dial: a blue needle at the device's

own heading and a red needle at the nearest repeater — or at an **active SOS

beacon**, which outranks every routine site, because an operator looking at the

phone is looking for a person — together with the digital true and magnetic

readouts, the local variation, and the target's distance, frequency, and

steering instruction:

T282828

With an unresolved beacon in the registry the red needle and the vector line

switch to it instead:

T282828

The dial is drawn entirely with inline SVG and CSS — no image, no external font,

no script from a network — so it renders on a phone in airplane mode with the

browser it already has. It refreshes on the same ten-second cadence as the rest

of the page, and a node with no compass shows a sentence in place of the dial

rather than a needle pointing at nothing.

The chat box is restricted to the commands whose answers are computed

in-process — T383838med (first aid), T383838tower near, T383838tide near, T383838sun, T383838whereami,

T383838morse, T383838conv, and the rest of the offline field set. A command that needs a

live radio link answers with a line saying exactly that, rather than failing

obscurely.

The SOS button asks for confirmation, then raises a RED beacon through the

same registry command the radio uses: the beacon is persisted, every room of

every live hub session is alerted, and the LXMF dispatch copy is queued when one

is configured. A device with no hub currently connected still records the beacon

and says that no room could be alerted.

298

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838help | T383838@gobot help [command] | Lists all available commands, or provides comprehensive help for a specific command (e.g. T383838@gobot help loc). |

| T383838ping | T383838@gobot ping | Responds T383838pong to verify link liveness and latency. |

| T383838uptime | T383838@gobot uptime | Reports bot uptime, hub connection duration, and hub identity hash. |

| T383838whoami | T383838@gobot whoami | Displays your nickname and full 32-character identity hash as seen by the current hub. |

| T383838botinfo | T383838@gobot botinfo | Details the bot's identity hash, version, connected hubs, and active rooms. |

| T383838rooms | T383838@gobot rooms | Lists all rooms the bot is currently participating in. |

| T383838members | T383838@gobot members [room] | Lists members reported by the hub in the specified room. |

| T383838seen | T383838@gobot seen <nick|hash> | Shows the timestamp when a given nick or identity hash was last seen speaking in joined rooms. |

| T383838id | T383838@gobot id | Displays the bot's full identity hash and configured trigger nicknames. |

| T383838more / T383838next | T383838@gobot more | Shows the next page of the last T383838search, T383838near, or T383838list answer (see Low-Bandwidth Pagination). The pending page is remembered per identity for 5 minutes; with nothing pending the answer is T383838no more pages or search expired. |

150

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838dn / T383838dnotice | T383838@gobot dn <nick|hash|me> <text> | Sends an encrypted direct notice (T383838K_DST) to the specified client. |

| T383838dnoticecap | T383838@gobot dnoticecap [target] | Checks if the current hub supports direct notice delivery, and checks if a target user is online. |

| T383838dnoticeme | T383838@gobot dnoticeme <text> | Sends a direct notice to your own identity (tests private path functionality). |

| T383838msg / T383838lxmf | T383838@gobot msg <nick|hash> <text> | Queues an asynchronous LXMF message to an offline peer via propagation nodes. |

142

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838path | T383838@gobot path <nick|hash> | Queries the Reticulum routing table to report hops, next-hop interface, and path age to a peer. |

| T383838watch | T383838@gobot watch <name|hash> [ttl] | Requests a direct notice when a peer, node, or hub announces on the network. |

| T383838unwatch | T383838@gobot unwatch <n|all> | Cancels an active watch. |

| T383838watches | T383838@gobot watches | Lists your active announce watches and remaining TTLs. |

| T383838net | T383838@gobot net [max_hops] | Mesh directory: lists recently heard hubs, LXMF nodes, and NomadNet pages with hop counts. |

| T383838catchup | T383838@gobot catchup [window] | Delivers messages from joined rooms that were missed while you were offline. |

| T383838search | T383838@gobot search <term> [#room] | Searches recent room history for messages containing the given keyword. |

All location commands accept 5 coordinate notations without network connectivity:

1. Open Location Code / Plus Codes: T383838849VCWC8+R9

2. Decimal Degrees: T38383837.42205, -122.08409 or T383838N37.42205 W122.08409

3. Degrees & Decimal Minutes (DDM): T38383837°25.323'N 122°05.048'W

4. Degrees, Minutes & Seconds (DMS): T38383837°25'19"N 122°05'03"W

5. Maidenhead Grid Locator: T383838CM87uk

A sixth input form is a GCJ-02 "Mars coordinate" copied from a Chinese map

app (Amap/Gaode, Tencent, WeChat), marked with a T383838gcj: or T383838gcj02: prefix:

T383838loc gcj:39.9069,116.4038 or T383838tower near gcj:39.9069,116.4038. It is converted

back to the WGS-84 GPS position before anything else is computed. See

Cell & Radio Tower Finder.

346

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838loc | T383838@gobot loc <location> | Converts any supported coordinate format and outputs it in all five notations simultaneously. A position inside China also prints the GCJ-02 "Mars coordinate" that Amap and Gaode expect. |

| T383838dist | T383838@gobot dist <from> <to> | Calculates great-circle distance (km, statute miles, nautical miles) and forward/reverse bearings between two points. |

| T383838proj | T383838@gobot proj <origin> <bearing°> <distance> | Dead reckoning: calculates the destination coordinate from a starting location, course, and distance (e.g. T383838@gobot proj CM87uk 045 15km). |

| T383838whereami | T383838@gobot whereami [location] | The operational location card: Plus Code, coordinates, Maidenhead grid, elevation, the heading, fix status, local solar time, and the sunset countdown. With no argument it uses the live GNSS fix. Also accepted as T383838/whereami. See The Go Reticulum Lifesaver. |

285

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838sun | T383838@gobot sun [location] [date] | Computes UTC sunrise, sunset, civil twilight dawn/dusk, and total daylight hours for any location on Earth. With no location it uses the live GNSS fix, and a bare date (T383838sun 2026-06-21) keeps the date while taking the position from the fix. |

| T383838moon | T383838@gobot moon [location] [date] | Reports moon phase, illumination percentage, lunar age, moonrise/moonset, nighttime illumination rating, and upcoming spring/neap tides. |

396

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838sos | T383838@gobot sos [loc] [RED|YELLOW|GREEN|INFO] [details] | Broadcasts an emergency distress beacon across all rooms, confirms receipt to sender, persists beacon to disk, and dispatches via LXMF to emergency responders. With no location, and with a live GNSS fix, the beacon is raised at the operator's own position (RED by default) and the receiver facts are attached. |

| T383838sos list | T383838@gobot sos list | Lists all active distress beacons. |

| T383838sos clear | T383838@gobot sos clear <id> | Resolves and clears an SOS beacon (restricted to the original sender). |

| T383838checkin | T383838@gobot checkin <loc> overdue <duration> <note> | Arms an overdue dead-man timer (e.g. T383838overdue 4h). If not cleared before expiry, the bot raises an automatic overdue alarm. |

| T383838checkin ok | T383838@gobot checkin ok | Clears your active overdue check-in timer. |

| T383838sitrep add | T383838@gobot sitrep add <loc> <HAZARD|RESOURCE|SHELTER|ROAD|INFO> <text> | Files a geolocated situation report to the 7-day tactical board. |

| T383838sitrep near | T383838@gobot sitrep near <loc> [radius_km] | Finds situation reports within the specified radius, sorted nearest-first. |

275

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838firstaid / T383838rx / T383838med | T383838@gobot firstaid <topic> | Offline clinical decision-support cards for wilderness medicine: T383838bleed, T383838cpr, T383838triage, T383838shock, T383838hypo (hypothermia), T383838heat, T383838burns, T383838water, T383838snake. T383838med is the short name the field guides and the portal chat box use. |

| T383838coldwater | T383838@gobot coldwater [temp] | 1-10-1 cold water survival rule and swim failure timelines for water temperatures (e.g. T383838@gobot coldwater 48F). |

| T383838signal | T383838@gobot signal [air|sound|light] | Distress signaling standards: ground-to-air visual markers (V, X, N, Y), whistle cadences, mirror/torch patterns. |

| T383838morse | T383838@gobot morse <text> / T383838morse -d <code...> | Bidirectional Morse code encoder and decoder. |

| T383838conv | T383838@gobot conv <val><unit> <target> | Tactical unit conversions: barometric pressure (T38383829.92inHg → T383838hPa), distance, speed, fuel/water weight, and battery watt-hours (T3838385000mAh@3.7V → T383838Wh). |

194

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838weather / T383838wx | T383838@gobot weather <location> | Live conditions from plain-text weather feed. |

| T383838tide | T383838@gobot tide <station|coords|place> [date] | 48-hour high/low water predictions, Rule of Twelfths hourly depth interpolation, and spring/neap tide classification. |

| T383838tide search | T383838@gobot tide search <query> [page] | Finds a station offline by name, state, or id, four per page. |

| T383838tide near | T383838@gobot tide near [place|coords|pluscode] | The three closest stations, with distance in nautical miles and bearing. With no argument it uses the live GNSS fix. |

| T383838tide list | T383838@gobot tide list [state] [page] | Every station, or one state's (T383838CA, T383838OR, T383838WA, T383838AK, T383838HI, …). |

| T383838buoy | T383838@gobot buoy <buoy_id> | Real-time ocean buoy sea state: wave height, dominant wave period, swell vs chop classification, water temp, pressure trend. |

| T383838buoy search | T383838@gobot buoy search <query> [page] | Finds a buoy offline by place, id, region, or state. |

| T383838buoy near | T383838@gobot buoy near <place|coords|pluscode> | The three closest buoys, with distance in nautical miles and bearing. |

| T383838buoy list | T383838@gobot buoy list [region|state] [page] | Every buoy, or one region's (T383838CA, T383838HI, T383838AK, T383838GOM, T383838ATL, …). |

| T383838river | T383838@gobot river <usgs_gauge_id> | Stream gauge stage, discharge rate, 3-hour trend, and official NOAA river forecast flood categories. |

| T383838metar | T383838@gobot metar <ICAO> | Decodes raw aviation weather reports into wind, visibility, temperature, dewpoint, and altimeter setting in both units. |

| T383838metar search | T383838@gobot metar search <city|name|code> [page] | Finds an airfield offline by city, airport name, ICAO code, or IATA code (T383838denver, T383838heathrow, T383838KDEN, T383838LHR). |

| T383838metar near | T383838@gobot metar near <place|coords|pluscode> | The three closest airfields, with distance in nautical miles and bearing. |

| T383838metar list | T383838@gobot metar list [state|country] [page] | Every airfield, or one state's or country's (T383838CO, T383838CA, T383838TX, T383838GB, T383838JP, …). |

| T383838wxalert | T383838@gobot wxalert <place|zone> | Queries active National Weather Service severe weather warnings and advisories. |

| T383838spacewx / T383838solar | T383838@gobot spacewx | Reports Solar Flux Index (SFI), Sunspot Number (SSN), K-index, geomagnetic storm levels, and recommended HF propagation bands. |

| T383838launches | T383838@gobot launches [upcoming|past] | Schedules and status of upcoming orbital space launches. |

| T383838flight | T383838@gobot flight <flight_num> | Real-time ADS-B flight telemetry: route, altitude, groundspeed, climb rate, and squawk code. |

669

| Command | Syntax | Description & Example |

|---------|--------|-----------------------|

| T383838tower / T383838repeater / T383838cell / T383838mast | T383838@gobot tower near [place|coords|pluscode] | The three closest communications sites, with the distance in kilometers, the bearing, the service, the frequency with its offset and tone, and the place. Entirely offline; a site inside China also prints the GCJ-02 coordinate for Amap/Gaode/WeChat. With no argument beyond T383838near it uses the live GNSS fix, and with a live compass heading it adds the relative steering instruction that aims an antenna — T383838[Turn 15° RIGHT · 1 o'clock]. See Cell & Radio Tower Finder and Radio direction finding. |

| T383838tower search | T383838@gobot tower search <query> [page] | Finds a site offline by callsign, identifier, name, city, pinyin place name, state or province, frequency, or operator (T383838sutro, T383838beijing, T383838sichuan, T383838145.150, T383838china mobile). |

| T383838tower list | T383838@gobot tower list [country|region] [page] | Every site, or one country's (T383838US, T383838CN, T383838GB), one country's by name (T383838china, T383838germany), one US state's (T383838CA, T383838CO) or its name, or one Chinese province's (T383838BJ, T383838GD, T383838SC, T383838XJ). |

| T383838tower info | T383838@gobot tower info <id> | One site in full: the exact WGS-84 position, the GCJ-02 position when the site is in China, the Maidenhead grid, the elevation, the frequency, the offset, the tone, and the operator. |

To run T383838gorrcbot as a persistent Linux service:

Create T383838/etc/systemd/system/gorrcbot.service:

T282828

Enable and start the service:

T282828