rich/MeshTerm

0 Fork 0

Files

T

Jean-Pierre MartineauandClaude Opus 5.5 19c910bbde Rooms get their own page, and a room that doesn't answer is explained

Joining a room moves out of Chat into a Rooms page beside Channels. It
lists every room server the radio knows, joined ones first, with each
room's access, unread count, last post and last-heard time. Each room
has a page: join, log in again, change password, open the board, forget
it, or delete its stored posts. Chat now lists only joined rooms, the way
it lists only channels on a slot, and only a joined room raises the
unread badge. chat join becomes rooms join, alongside rooms list and
rooms forget.

"No reply" told the reader nothing, because a room is just as silent for
a wrong password as for a login that never reached it. Testing on
hardware showed the commonest cause is neither: a login sent along the
route the radio had learned met silence, and the same login by flood was
accepted in eleven seconds. A silent login is now explained from what is
known: how it went out, when the room was last heard, and whether this
password has worked before. It offers the one next step that evidence
points at:
- Try by flood, after a learned route met silence. The radio forgets
  the route (local, nothing transmitted), then sends the login once.
- Try again…, after a flood met silence. The prompt reopens with the
  password filled in, so Enter resends it and typing replaces it.
- Add it & try again, when the radio doesn't hold the room as a contact.
Every retry is a button press, and none is ever sent on its own. A
password over 15 bytes is refused at the prompt, since MeshCore sends
only the first 15.

On the board, a failed or unfinished login used to leave the compose
line taking posts the room would drop. It now opens only while we are in
and may post, and otherwise says why and what to press. Opening a joined
room that has gone quiet logs in in the background. ^L runs the
explained flow.

Underneath, the login exchange listens for the radio's own confirmation,
matched to the login by its expected ack. It records whether the login
went by flood or along a route, or the radio's reason for not sending it
at all. This also corrects the debug log: "send unacknowledged" read the
library's wait for the *answer* as the send. On hardware the radio
confirms in under 0.1 s. Device.reset_route is new. The simulator learns
routes, can be given a stale one, and refloods.

Refs: #24
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-05 02:07:10 -04:00

10 KiB

Raw Blame History

What MeshTerm does

Every screen the menu offers, and the command that does the same job without it. This is the catalogue; the command line is the manual for the scripted half of it.

MeshTerm's menu asks one question — what would you like to do? — and its six sections answer it in two halves. The first three name a doing: Message, Watch, Explore. The last three name whose a setting is: This node, the radio in your hand; Other nodes, someone else's over the mesh; and This app, the program in front of you.

Every interactive screen is listed here with its scripted equivalent, where one exists.

💬 Message — the people on the other end

Feature	What it does	Scripted
💬 Chat	Live full-screen channel and direct messaging — a scrolling transcript with a pinned input line where sent and received messages stream together. The rooms you've joined are here too, each post shown under whoever wrote it. Every message is logged; unread counts show in the menu header.	`meshterm chat send / history / list / listen`
📻 Channels	Create, join, reorder, mute, and share mesh channels — with QR codes and `meshcore://` share links. Give a channel a send scope and its messages are flooded into one region, relayed only by the repeaters that carry it.	`meshterm channels list / add / join / import / share / clear / scope`
📌 Rooms	Every room server your radio knows. A room server is a message board on a radio that keeps the latest posts and sends you the ones you missed. Join one with its password; when a room doesn't answer, MeshTerm explains what it knows and offers the next thing to try, such as resending by flood when the route your radio learned has gone stale.	`meshterm rooms list / join / forget`
📨 Courier	Store-and-forward outbox for contacts that aren't reachable yet. Queue a message; it goes out (with ack tracking and polite exponential backoff) the moment the contact is next heard, or at a scheduled time.	`meshterm courier queue / list / send / cancel / clear`
👥 Contacts	This node and its known contacts — a recency heat-map, overheard packet counts, and full public keys with the path-hash prefix highlighted. The scripted listing is the contacts alone (this node is `meshterm info`'s answer, in far more detail).	`meshterm contacts`

📊 Watch — what the mesh is doing, and what it did

Feature	What it does	Scripted
📊 Dashboard	The live mesh overview: a two-hour all-packet activity chart with a pulse line, session traffic tallies by packet class, and window RF health beside the radio's own live numbers. Repaints every second.	—
📰 Live feed	Every packet as it arrives, newest first: time, what the frame is (its parsed payload class), and what it is about — the node for an advert, the channel for a channel text, sender → recipient for a direct message or a request, the tag for a trace — with reception quality beside it, and the region a scoped flood was sent into. Enter opens any row in the packet viewer, route graph and all.	—
🚨 Watchtower	A passive sentinel over the nodes you star: silence alarms when a watched node goes quiet, SNR-sag warnings when reception degrades, recovery notes when it returns, and a heads-up when a node is heard for the first time. Runs in the background all session; unacked alerts show as a header badge.	—
⏳ Time machine	Everything the recorder ever heard, as braille charts: reception volume, the median-SNR band, hour-of-day rhythm, packets and nodes per day, and first-ever arrivals — over a switchable 24h / 7d / 30d / all-time window (on the PicoCalc the windows stop at 30d), per node or mesh-wide.	—
🎧 Monitor	Passive recording is always on in the app. On the CLI, capture a bounded foreground window, tailing each overheard packet and summarising when it ends. It transmits nothing — it only listens.	`meshterm monitor --seconds 60`

🧭 Explore — where the nodes are and how they reach each other

Feature	What it does	Scripted
🌍 Map	Located nodes plotted over a real OpenStreetMap street basemap rendered as Unicode braille (streets, rivers, place names). Pannable and zoomable; repeaters highlighted and drawn on top. Falls back to a blank grid offline.	— (a map is a picture; `meshterm contacts` lists the same nodes)
🌐 Mesh walk	The mesh's observed shape, walked one node at a time: an evidence graph built from trace walks, firmware routes, overheard relay chains, and repeater neighbour tables. SNR-coloured braille edges, quality bars, Enter to walk, ⌫ to backtrack, type to find any node. The map answers where; the walk answers how it hangs together.	—
🎯 Trace target	A live trace screen: pick a target and watch each trace stream in hop by hop, with running per-hop medians and reliability. Compose or force a route through specific repeaters. A trace transmits exactly once (repeaters can blacklist nodes that burst) — sample more by running it again.	`meshterm trace --target …`
👣 Trace path	The other half of tracing: compose the whole circuit by hand — out and back whichever way you choose — and walk it. The path composer suggests each next hop from the links actually observed, strongest first, and can fetch a repeater's neighbour table over the mesh when you hold its admin password.	`meshterm trace-path --path …`
🏆 Trophy case	Every trace that comes home is scored, on seven boards: longest distance, farthest node, longest single leg, most nodes (with and without revisits), weakest surviving link, and biggest enclosed loop. Records are kept per hash width, and a record walk must be a trail — no link crossed twice the same way.	`meshterm records`

🔧 This node — the radio in your hand

Feature	What it does	Scripted
📋 Device info	The connected companion's identity and full radio configuration at a glance.	`meshterm info`
🔧 Device config	Every setting the companion firmware exposes — name, radio, client repeat, auto-add, telemetry, custom variables — staged for review and applied in place, plus the operations on the box itself: clock sync, TOML backup/restore, the identity key, reboot, and factory reset, each acting the moment it's confirmed, with destructive ops gated. Laid out like Repeater admin, so the radio in your hand and one over the mesh are configured the same way.	`meshterm config` / `config set <key> <value>` / `config backup` / `config reboot` / …
📡 Send advert	Announce this node to the mesh — a zero-hop or flood advertisement, or share this node's contact card as a QR code.	`meshterm config advert` / `config share`
🔌 Devices	Not a menu screen. The companion is picked on the startup splash, which enumerates serial and Bluetooth LE companions (or auto-selects the only one present), adds a network (TCP) companion by host:port, and remembers the last good default. A dropped link is detected live and offers to reconnect. `meshterm devices` lists what discovery finds.	`meshterm devices`

🗼 Other nodes — someone else's radio, over the mesh

Feature	What it does	Scripted
🗼 Repeater admin	Set up remote repeaters and room servers over the mesh: log in (remembered or prompted password), then a config-style editor speaking the node's text CLI — including repeater-only knobs (TX delay, airtime factor, advert intervals) — plus one-shot actions and a readline remote command line. A Regions page edits the repeater's region tree: which regions it relays floods for, whether it relays unscoped floods, its home and default scope.	`meshterm repeater-admin <node> <command…>`
🔖 Regions	Not a menu screen. A repeater's node page lists the regions it carries and asks it once, without logging in (it answers only a neighbour, or over a known route); the packet viewer, message paths and live feed name the region a flood was scoped to.	`meshterm regions <node>`
📶 TX optimize	Sweep a remote node's transmit power live — coarse, then refine, then verify — watch each level land, and decide whether to apply the winner. The scripted form applies the winner unless told not to.	`meshterm tx-optimize --path … [--no-apply]`

⚙ This app — the program in front of you

The last of the three, and the one nothing on the mesh can answer. Preferences leads it because it is the only row here that changes MeshTerm rather than describing it; the written pages close it.

Feature	What it does	Scripted
⚙ Preferences	How MeshTerm behaves, in eight groups: Device, Sending, TX optimize, Watchtower, Map, History, Display, and Diagnostics. Grouped and staged, saved by one action at the bottom, and written to `preferences.toml` as only the values you changed. Configuring MeshTerm has the detail.	`meshterm preferences show / set / reset`
🩺 Diagnostics	Everything a bug report opens with, in one block: which build this is and how it was installed, the OS, the terminal and its size, the boot-time verdicts that show on no screen (icons, powerline, platform flavour, and why), the radio and its link, and how much history is stored. Nothing private — no keys, passwords, positions, or contact names; the mesh is described as per-table counts and the span they cover. `s` saves it beside the log for attaching.	`meshterm diagnostics [--out PATH]`
📖 About MeshTerm	What MeshTerm is, where it came from, and the terms it ships under — including the map and font credits and the licence URL.	`meshterm about`
👤 About the author	The person behind MeshTerm, on the mesh and off it.	`meshterm about-author`
🔗 Join Discord	The community server: one invite link, and a QR of it for a phone to read.	`meshterm discord`
💰 Support MeshTerm	What keeps MeshTerm going, and the ways — paid and unpaid — to help it along.	`meshterm support`

10 KiB Raw Blame History