Release v1.7.7

What's New in 1.7.7

Message storage moved to a real database

This is the big one. Messages, contacts, discovered nodes, and channel data no
longer live in app preference files — they're now in an embedded SQLite database
via Drift. Every write is a single row instead of a rewrite of the whole
conversation, so history can't be clobbered by an unlucky save, and the app reads
what it needs instead of loading everything into memory at startup.

Your existing history migrates automatically the first time you open each
conversation after updating. Nothing to do, and nothing is thrown away.

Channels are identified by their key, not their slot number

Channel history is now filed by the channel's encryption key rather than the slot
it happens to occupy on your radio. Reorder your channels, delete one and add
another in its place, or run two channels with the same name and different keys —
messages still land in the right conversation. Two channels whose names collide
on the air are now told apart correctly, so a channel can no longer go "deaf"
because another one shares its hash.

MeshTrax also refuses to create a channel with a key you already have, and checks
your radio's slot table after each sync to warn you about duplicates.

Sending is more reliable

Channel messages sent before the app finished verifying your channel list are no
longer stranded or silently dropped — they queue and go out once the list is
ready. Sends now also wait longer for a quiet moment before transmitting, so a
message composed right after a burst of incoming traffic is less likely to
collide with mesh traffic still in flight.

Path tracing

You can now jump straight from a path trace to Set Custom Path. Traces that fail
tell you so with a toast instead of leaving the previous result on screen, and a
route that already makes a round trip is no longer doubled in the display. The
contact picker used to reach path trace was also fixed.

Also in this release

Repeater discovery waits 30 seconds instead of 10, so slower repeaters actually
show up. Repeater CLI commands can return sooner instead of always waiting out a
15-second floor. Line-of-sight endpoint dropdowns are sorted alphabetically.
Unread badges are computed directly from the database, so they stay consistent
with what you actually see in the conversation.

Full Changelog: v1.7.0...v1.7.7
ub.com/venamartin/meshtrax/compare/v1.7.0...v1.7.7