Commit Graph
1124 Commits
Author SHA1 Message Date
Jean-Pierre MartineauandClaude Opus 5.5 d08513aa69 contacts --sort takes place and hash; the Archived list gets the PLACE column
The CLI sorts on the same ring as the Contacts screen (name, heard, packets,
place, hash). The ring moved to ui/widgets.py so the CLI loads no TUI code, and
ordered_contacts sorts by place (no place last) and by key.

The Archived list reads NAME · ARCHIVED · PLACE · KEY, sorts by place, cuts no
value and pans with ←→, like the Contacts list. The place fill and its live
refresh moved from ContactsScreen into ContactListScreen, so any list that
declares the PLACE lane gets them from places=.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 17:28:01 -05:00
Jean-Pierre MartineauandClaude Opus 5.5 2df3dd2c39 The purge removes mock nodes' places; the place tests get docstrings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 03:11:16 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 df06fd1a89 The contacts command tolerates a context with no place service
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 03:06:56 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 538b0a5a69 The map's find filter also matches a node's place
MapMarker carries a place, open_map reads it for each marker, and both the screen
and the renderer match label or place through MapMarker.matches.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 03:05:06 -05:00
Jean-Pierre MartineauandClaude Sonnet 5.5 7dd7cb5a62 ^N shows the places of the nodes on Node detail, the packet viewer, Live feed, and Trace
Each screen opens with node names and keeps its own choice. Node detail acts only on
the Routes tab (F1). The packet viewer changes its via line and its from/to chips (F1).
Live feed changes the endpoint chips of an addressed packet (F1). Trace changes its
route lane and its per-hop links (F1). Each hint and chip shows only where a line has
a named hop.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-03 03:01:12 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 9626d06a3f The contacts command gives each node's place, and the node object has a place key
fields.node adds place (null when unknown) to its machine object, and the plain
face gets a PLACE column before KEY. The command reads stored places only.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 03:00:55 -05:00
Jean-Pierre MartineauandClaude Sonnet 5.5 c3174b6fbb ^N shows the places of a path's nodes on the Trophy case, TX sweep, Mesh walk, and path composer
Each screen keeps its own PlaceToggle and opens with node names. The record page
and the board rows, the sweep route line, the walk trail, and the composer's route
preview go through placemode.placed. The hint and the lane chip show ^N only where
a path line has a node that can change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-03 02:59:51 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 07c8bc1d23 Contacts show each node's place before its key, cut no value, and pan with the arrows
A PLACE lane sits before KEY. The Contacts list sizes its lanes to their content, and the
table (header and rows) pans with the left and right arrows while the mark column and the
name stay. The place sorts, and the find-as-you-type filter matches it.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:57:40 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 366fff0d4a ^N shows the places of a path's nodes on Message paths
Place mode changes a finished path line's hop labels to each node's place
(ui/placemode.py); a hop keeps its key and colour, a named hop with no place
reads (Name), an unnamed hop keeps its hash, our ★ stays. The node resolver
now also tells which node it named, so a shared one-byte hash finds the same
node's place. Message paths is the first screen: ^N, its hint, and a lane chip.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:48:51 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 d541c6d3fd The node page shows a node's place, and the user can set it
A place row sits above where on the Info tab, read at each paint so a place
the finder answers after the page opened still appears. Set place… types a
place that wins over the found one (blank clears it, marked · typed).

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:47:38 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 6c63697e21 Nodes get a place: the named area nearest their location
A background job finds the place of each node that advertises a location
(Villeray, Montréal; a village; a peak near its summit). The map tiles give
the first answer offline; Nominatim corrects it when online (place_source,
default tiles then Nominatim; nominatim_url). Places are stored in the new
node_places table, a typed place in places.json wins over a found one.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:47:05 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 4ded134c05 The bulk clock sync shows each node's progress in one dialog
"Sync their clocks…" now opens a dialog that lists every managed
repeater and room from the start: ○ waiting, a spinner with what it
waits for (the transmit cooldown, the login, the command), then ✓ with
the node's reply or a red ✗ with the reason. Long reasons wrap under
the name. Esc stops the run after the node in progress; the OK chip
closes the dialog once the run is done.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:31:02 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 e00931bb18 "Sync their clocks…" covers every managed repeater and room
The bulk row now shows whenever the page has a managed repeater or room
server, and it syncs each one whatever its offset: a repeater with no
battery restarts from its build date at each power cycle, and the page
only learns that at its next advert. Managed companions still have no
clock sync command, so they are never included.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:12:35 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 5d20fe49b5 The Clock drift page can sync all managed clocks at once
The Managed nodes section ends on "Sync their clocks…" when a managed
repeater or room server is out of sync or has no sample. One confirm,
then each node in turn: a cancellable transmit-cooldown wait, a quiet
login with its stored password, and "clock sync"; one summary names
each result. "Adverts refused" moves to the end of the page.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 02:02:27 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 b4ea549fb0 The Clock drift histogram goes on top of the page
"All clocks" now opens the page, so the shape of every clock comes
before the lists of single nodes; Managed nodes is the first list under
it, then Adverts refused, Out of sync, and Senders with no key.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 01:41:06 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 e830f2239d A room whose clock went back can be asked for all its posts again
A room stamps posts with its own clock and sends only posts newer than
the companion's sync_since, so after its clock goes back (often a
reboot) it sends nothing new. When a room's newest stored post is later
than its clock now (from its clock offset), its node page shows
"posts  blocked" and offers "Ask for all its posts again…". The repair
removes the room contact and adds the same raw record back, since the
firmware gives only a new contact a sync_since of zero, then logs in
with the stored password. Device.reset_room_sync tries the add twice and
says plainly if the room is left off the device.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 01:03:33 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 6e07b08c25 Managed nodes get a name, a 🔑 mark, and node page repairs
A node whose admin password MeshTerm stores is now a "managed node": a
🔑 beside the type mark in the Contacts list, the admin picker (its
first section, renamed from "Remembered admins"), and the node page
header. The menu's "Other nodes" section is now "Managed nodes".

Contacts carry adverts_refused_until: the device's stored advert time
when it is in the future, so the firmware's replay check drops every
new advert. The node page shows it and offers "Accept its adverts
again…", which rewrites the device's own record with only last_advert
lowered (Device.accept_adverts_again). A managed repeater or room gets
"Sync its clock…". The Clock drift page lists refused contacts.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 00:46:40 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 d807109093 The Clock drift page puts managed nodes first, with column headers
Managed nodes are now the first section and are always listed: a node
with no sample in the window shows its newest offset from all history,
or "no sample". Each table has a header line under its section heading
(NAME / OFFSET / LAST, and OFFSET / # over the histogram, now under
"All clocks"). Older offsets do not count in the histogram or title.
The CLI lists each managed node too, with null fields when it has none.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 00:41:03 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 bdcdadc50c A Clock drift page shows which nodes have wrong clocks
A new Watch tool, "Clock drift" (meshterm clocks): a histogram of the
clock offsets in log steps on two sides, then the managed nodes, then
each other node out of sync, largest offset first; Enter opens the node
page. Channel senders with no key are listed by name. When most clocks
disagree with ours the same way, a note says our own clock may be wrong.
The CLI lists every sender with offset_s, samples, and flags. A new
clock_report_days preference sets the window. The demo world gets four
wrong clocks.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 00:25:07 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 adb79d051a Each node gets a clock offset, and its node page shows it
ADVERT packets now keep their own time (observations.sent_at, schema 22).
With the arrival times of messages, each advert, DM, and channel message
is a clock sample: the sender time minus ours. A channel sender counts
for the node its name resolves to, or under its name. A node's offset is
the median of its three newest samples. The node page's Info tab shows
"clock 3h 12m behind" in warn past the tolerance, or "in sync".

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-03 00:12:45 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 2cf0e09eb4 Old channel messages get their arrival time from the packet log
Rows stored before the arrival time had only the sender time, so a
wrong clock still put them on the wrong day. A one-time background
backfill decrypts the stored GRP_TXT packets with the device's channel
keys; a packet with the same text and sender time is the message, and
its first copy is the arrival. On a real history it matched 12,071 of
14,197 old Public messages in 1.6 s. DMs cannot be decrypted and keep
their sender time.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-02 23:28:55 -05:00
Jean-Pierre MartineauandClaude Haiku 5.5 8107256ebb A wrong sender clock shows the arrival time with a ? mark
A received message now keeps its arrival time (received_at) beside the
sender time, and whether it waited in the companion's queue. Heard times,
the Messages list order, channel activity, and the packet-log search use
the arrival time, so a DM from a clock a year ahead no longer pins its
contact at "heard now". The transcript shows a corrected time as 12:31?,
and a picked message says what the sender's clock wrote. The CLI history
carries the same mark; its JSON gives both times. clock_tolerance_s
replaces ADVERT_FUTURE_SKEW_S as a preference.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-11-02 23:09:47 -05:00
Jean-Pierre MartineauandClaude Opus 5.5 a493a6a5eb Keep the calibration ladders in scripts/ladders, with the method
A ladder draws the candidates for a visual value side by side through
MeshTerm's own renderer and live constants, so JP can choose by eye.
The two that set constants are kept: hue_ladder.py (the node wheel's
lightness, 0.72 on 2026-10-29) and seam_ladder.py (SEAM_BLUR, rebuilt
from the 2026-09-16 tool), with contrast.py for the measurement that
comes first and ladderkit.py for what they share.

launch.ps1 opens a ladder in a new Windows Terminal window and waits
for the ladder's marker file; -Snap also takes a screenshot through
snap.ps1. It avoids the three traps that broke the launches this week:
wt quoting a forwarded command line as one file name, the tab
inheriting Claude Code's NO_COLOR=1, and Rich falling back to the
16-colour console API when virtual terminal processing is off. The
README explains the method and the traps.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-29 01:10:16 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 598e53b488 Node hues share one OKLab lightness, so every name and chip reads alike
The spectrum was an HSV wheel at one saturation and value, which is not
one lightness to the eye: blue names sat at OKLab L 0.55 and yellow at
0.93. A chip's fill is its label at CHIP_LIGHTNESS of that lightness, so
chip contrast followed the label, from APCA Lc 19 on blue to 64 on
yellow.

Each byte now keeps its HSV hue angle and chroma at OKLab L 0.72, with
the chroma fitted where the gamut cannot hold it. JP chose 0.72 on a
ladder of wheels from 0.70 to 0.85. Every name reads equally light and
every chip lands at Lc 34 to 41.

The 256 colours are written out as _NODE_SPECTRUM, because computing
them costs about 14 ms here and _IDENTITY_STYLES needs all of them at
import, which would slow every start on the handhelds. A test holds the
table to _spectrum_hex, and checks one lightness, 256 distinct hues, no
console-slot collision, and that each hue angle is kept.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-29 01:05:13 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 f296413a5e A thin chip seam is halfway between the chip's label and its fill
The thin chevron between two chips of one colour took the previous
chip's label colour. It now takes the OKLab midpoint of that label and
the chip's fill (oklab.midpoint), so the line is softer than the text.
The 16-colour console keeps the label, because it has no slot between
a bright hue and its dim twin.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-29 00:20:00 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 0d09a364cd MeshTerm 0.11.5
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-22 03:15:55 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 544156968d The Courier outbox filters as you type again, and a wide footer keeps Esc
Typing narrows the outbox again, and its footer says so. With the scroll
atom, the footer of an entry row is wider than 72 cells, which JP
accepted. The footer line no longer cuts a hint that is too wide at the
edge, which took Esc with it: it drops atoms instead, as the splash
already did. The outbox drops "Del delete" first.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-22 01:09:55 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 53ffb984cb The Courier outbox shows each message and pans instead of cutting
Each row now carries a third column, MESSAGE, after TARGET and TRIGGER
(or OUTCOME). Nothing is shortened to fit: the rows and their headers pan
together with ←→, and the footer says so while the table runs past the
edge. The outbox no longer filters as you type, which keeps the footer
within 72 cells.

A column header that pans now pins with its section heading, as a
header that does not pan always did.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-22 00:52:40 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 0b931e7cc4 The Courier outbox is a TARGET and TRIGGER table, and Enter opens the message
Each section of the outbox now has column headers: TARGET and TRIGGER for
waiting entries, TARGET and OUTCOME for finished ones. The rows no longer
show the message. Enter on a waiting entry opens it to edit (the courier
holds the entry while the prompt is open, so the old text cannot go out
meanwhile), and Enter on a finished one shows it. Del deletes an entry
after a red confirm, and ^R sends a waiting entry now; on the PicoCalc
they ride F3 as Send, with Delete behind it. On a narrow screen a long
name gives cells to the trigger and breaks off on its crack.

The message field has the colours of the chat's compose line: a white
prompt mark and white text.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-22 00:22:05 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 1b30f353c6 A cut in the text beside a chip ends on an ellipsis, not on a stray crack
When a row was a chip followed by text (a Courier entry: the recipient,
then what it waits for) and the text ran past the screen, the cut looked
back for a chip fill, found the chip far to the left, and drew a half
block in its colour at the right edge. The crack now forms only inside
the path that the row stamps, so a cut in plain text gets the ellipsis.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-22 00:22:04 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 284c2718c6 MeshTerm 0.11.4
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-20 00:24:12 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 8f3f07276b Rewrap a docstring line that ruff found too long
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-20 00:01:45 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 8dff5bbb29 The selected chat message whitens its author chip and its unknown mentions
The author chip of the selected message's group now turns its label white,
as the message's text does, and goes back when the selection leaves the
group. A mention of an unknown node turns white too: its grey fill already
says the node is unknown, and white reads better on it than black.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-19 23:59:45 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 7264a71104 The mention chips of a selected chat message go white with its text
In a channel, a DM, or a room, the selected message's text is white, and
now its mention chips follow: the label turns white and the fill stays, so
the chips still tell one node from the next. Arrow mode whitens the label
the same way. A mention that no key can place keeps its grey, as on every
selected row.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-19 23:48:59 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 59273a6b29 A locked author's sender chip carries the padlock, as ours carries the star
In a channel, a DM, or a room, the chip of a sender that is a locked
contact reads 🔒 Name (⚿ on the PicoCalc), in the place of the ★ on our
own chip. The transcript cache now compares the locks, so a ^K or a lock
from the node page redraws the chips on the next paint.

The padlock is one constant, marks.LOCK_ICON, shared with the Contacts list.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-19 23:40:32 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 793bc26436 ^K on the Contacts list locks or unlocks the highlighted contact
The same key as in a conversation. The row gains or loses its padlock in
place, with no confirm, and the next ^K reverses it. On the handhelds, Lock
(or Unlock) rides Shift+F2, as in a channel and a DM.

The hint names ^K only where it fits without dropping another atom. That
rule now lives in one helper, menus.splice_if_room, which the archive
preview uses too.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-19 23:27:05 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 daa26be5df ^K in a conversation locks the author of the selected message
In a channel, a DM, or a room, ^K toggles the lock of the contact that wrote
the selected message, so the archive sweep never takes it. The hint says
^K lock or ^K unlock, but only where it fits without dropping another atom,
and the status line confirms what the key did.

On the handhelds, Lock (or Unlock) rides Shift+F2 in a channel and a DM. A
room keeps Log in there, so the Author page that a conversation opens now
carries the lock row, and no other management verb.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-19 23:18:57 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 60a2df727a Shift+Delete in the archive preview locks a contact as well as sparing it
Delete keeps a contact out of this sweep only. Shift+Delete removes the row
the same way and stages a lock, so no later sweep takes the contact. The
locks are written on Apply with the archive; Esc and Back ask before they
discard them. A preview left with only locks applies them without the amber
confirm.

The footer names ⇧Del lock only when the hint still fits 72 cells, and a
contact row now says Enter open, since Enter opens its node page. On the
handhelds, Lock rides Shift+F3 behind the Delete chip.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-19 18:14:39 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 87bf929ac4 The Cardputer's battery gauge stays on through the Cap's noisy bus
On battery with the Cap on, 79% of the gauge reads failed, in groups of
up to 110 s. The poll read 3 times in 11 s and then waited 20 s, so it
missed the good periods, and after 7 failed polls the gauge went away.

- After a failed read, the next read comes after 5.5 s, not 20 s.
- The last good reading stays for 10 minutes instead of 7 polls.
- A change of the charging flag waits for a second read that agrees,
  because a garbled read said Charging while the pack discharged.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-19 03:36:55 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 bdc60481ec A serial link that dies while its port stays listed opens the reconnect dialog
When a laptop wakes from sleep, the kernel can reset the USB device and hang
up the open port, but keep the same device file. The next write fails with
EIO, and the serial transport closes itself. The serial liveness check read
only the OS port list, so it said the link was up: no reconnect dialog
opened, and each command failed with no_event_received (issue #32).

The serial check now also reads the meshcore client's is_connected flag,
which the client clears when its transport is lost, as the BLE and TCP
checks already did.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-19 00:42:19 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 9d7c5340b5 MeshTerm 0.11.3
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-18 01:57:10 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 1d983013d7 No log keeps a password or a secret: the log file, the run log, or the remote history
Passwords, channel secrets, pairing PINs, and private keys reached the DEBUG log and
the runs table in plain text: every chat run stored its channel secret inside the
Conversation repr, and --password, --secret, channel links, and config set device_pin
were stored as typed. meshterm.core.secrets now hides each one as <secret> by its
shape (a secret-named key, record, set operation, or dataclass field; bytes; a Secret;
a remote `password`/`set guest.password` command; name=value in text), and by value
for each secret MeshTerm has read or sent. Both log handlers and the runs table go
through it, always. The remote CLI history keeps `password ` without its value. Schema
v20 hides the secrets that older versions stored.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-18 00:20:22 -04:00
Jean-Pierre MartineauandClaude Haiku 5.5 9e579424b4 The Anonymize preference masks the home folder and addresses in the log and diagnostics
Off by default. Each masked value keeps a tidbit (j*********u, DA:xx:xx:xx:7C:7C,
192.xxx.x.180, m******e.local), so two radios stay two radios. The log masks each
line as it is written; diagnostics take --anonymize/--no-anonymize, and the page
toggles with `a` (Shift+F3 on the PicoCalc). Refs #31.

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
2026-10-17 21:30:26 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 de5c833550 The README plays the demo video with the regions of the real mesh
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 18:32:03 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 fc58c58c09 The demo mesh uses the regions of the real mesh: na, can, onqc, qc, and yul
Each region is in the one before it, as on the real mesh: na > can > onqc > qc > yul. Every repeater of Montréal, Laval, and the south shore carries the five, and Mont-St-Hilaire, outside the city, has yul but does not relay it. The #montreal channel sends in yul instead of mtl. The invented regions (mtl, mtl-west, laval, south-shore, and the others) are gone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 18:23:30 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 1239242bb4 An Instagram video for each page of MeshTerm
scripts/reel_tours.py holds 21 tours, one for each page of the menu except the four written pages: chat, channels, rooms, courier, contacts, the dashboard, the live feed, the watchtower, the time machine, the map, the mesh walk, both traces, the trophy case, device info and config, send advert, repeater admin, TX optimize, preferences, and diagnostics. Each tour opens its page off camera, so the video starts on the feature, and has its own subtitles and post caption.

scripts/reels.py now takes several names or "all", keeps each recording in a folder with --recordings, plays the background traffic for the pages that show it, and gives the recording process the size of its terminal, so Diagnostics shows 72x38.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 17:01:01 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 b278ccfdc1 In the demo, the TX power of a repeater changes how well it is heard
TX optimize had nothing to find in the demo: the demo device answered each trace from the world's links and ignored the power that the sweep set on a repeater. Now a relay that TX optimize tuned is heard less well on the link that it transmits into, on the simulator's curve with its peak at 19 dBm, and a reading under the decode floor loses the trace. The repeaters of the world read 22 dBm, so the sweep finds a lower power with a better signal. A relay that nobody tuned keeps the readings of the world.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 17:01:01 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 e47f7b7ea8 The terminal of the Instagram videos fills the height of the phone
The terminal now has 38 rows instead of 28, and the series line, the terminal, and the subtitles fill the frame from y = 150 to y = 1530. Only the bottom 20% stays free for the name of the account and the caption of the post. The chat shows more of the conversation, and the QR code is larger.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 15:28:22 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 e766c1018b The Instagram videos say MeshTerm for MeshCore
The series line above the terminal is now "MeshTerm for MeshCore · Chat", so a viewer who does not know the name sees what MeshTerm is for.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 13:10:36 -04:00
Jean-Pierre MartineauandClaude Opus 5.5 fc7fd17554 The videos for Instagram come from a script
scripts/reels.py makes one vertical video of MeshTerm for each feature, from the demo mesh: 1080×1920, with subtitles in the picture and no sound, then a card with the wordmark and the website. The terminal has 72 columns, so its text is as large as a phone lets it be. It also writes a cover for the Reel and a caption for the post. The first video is the chat: the conversations, a live message, the paths of a message, a mention and its answer, and a link as a QR code.

screenshots.py now takes the grid of the terminal set as an argument, and its painter draws a full-width character that no font has (the "#" of a hashtag channel) as its ASCII form, instead of a box.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-17 13:03:36 -04:00