Jean-Pierre MartineauandClaude Opus 5.5
b9585e9b59
Hold-to-quit was the Cardputer's alone. It is now MeshTerm's gesture everywhere a key can be seen coming up, which a terminal never reports: - The emulator's window, for either handheld, which reads its own keys as the Cardputer's panel does. - A terminal's Esc, where the keyboard can be asked whether it is still down: GetAsyncKeyState on Windows, as the right-Ctrl rescue already asks, and EVIOCGKEY on Linux wherever the keyboard's event device opens (the PicoCalc, a uConsole, a user in `input`). It reads the key state only, no events. An Esc arriving while its key is still down is held back as a hold: delivered as it comes up, a box after a second, gone at three. The keyboard's repeats are part of the hold, a key typed during it goes in behind the Esc, and on a VT stream the last repeat, which prompt_toolkit can parse after the key is up, is dropped rather than going back a screen behind a box the reader just let go of. On macOS and over SSH Esc is unchanged. SIGTERM is a quit for the interactive menu on every platform now, not only under the Cardputer's launcher: a system shutting down gets the same clean exit, terminal and console font restored. EVIOCGKEY checked on the Cardputer's arm64 kernel; the Lyra was offline. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
11 KiB
11 KiB
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 |
Leaving MeshTerm
Quit at the bottom of the main menu leaves, after asking. Ctrl+Q asks the same question from any screen, and pressing it again while the question is up leaves at once.
You can also hold Esc. After a second, a box says Hold Esc to quit, with a bar that fills over the next two seconds. When it's full, MeshTerm closes, the same way Quit closes it. Let go before then and you're back where you were. While the box is up, MeshTerm doesn't start sending anything new over the radio, so a message that's going out finishes first. A quick press of Esc still goes back a screen, as always.
Holding Esc only works where MeshTerm can tell that a key is being held down, and a terminal never says when a key comes back up. These can tell:
- Windows.
- Linux, where you can read your keyboard's input device. That includes the PicoCalc, and
a uConsole or any other Linux computer where your user is in the
inputgroup. - The Cardputer Zero, and the emulator window for either handheld.
On a Mac, or over SSH, Esc works as it always did.