The QR scanner only read community codes, so the standard
meshcore://channel/add?name=...&secret=... links used by the official
app and sites like ipnt.uk were rejected as invalid community codes.
The scanner now also accepts channel links. It skips channels already on
the radio, asks before adding, and only uses a free slot after the
channel sync has finished. Also fills in the 59 untranslated strings in
all 17 locales.
Fixes#604
'Show link images in all chats by default' (default off) applies to
every channel and contact without an explicit per-chat choice: the
per-chat setting is now unset/on/off and resolves to perChat ?? default.
The 'Load images from links' master switch still overrides it.
'Load images from links' (default on) gates every link image fetch in
MessageUrlImageHelper: chat previews, notification images, ipfs://
resolution and pyx/ibb scraping. Per-chat toggles keep their values but
are disabled while it is off. IPFS uploads are unaffected.
Obscure the key with a show/hide toggle like the map API key dialog,
clear and restore the mask on focus changes instead of onTap, and only
save a key the user actually edited. Add ipfs.io as a named public
gateway preset now that it is the default.
Give IpfsUploadConfigException a reason enum mapped to l10n strings in
the attach flow, and show a localized empty-file message and generic
upload-failed message instead of raw English exception text.
Check before uploading that the link (from the gateway and a CIDv1-sized
placeholder) fits with the draft and the reply prefix, and tell the user
when it doesn't instead of cutting their text. The channel limit now
counts the @[name] reply prefix like the send path.
Only ';' needs encoding, so the title and body fit in one TXT string.
Values that aren't valid percent-encoding are used as-is instead of
hiding the banner.
removeContact now waits for the radio's reply and only drops the contact
locally when the radio confirms (or reports it doesn't have it), so a
lost command no longer leaves a contact that the next sync restores.
Failures are shown to the user. The delete dialog warns when the radio
auto-adds that contact type, since the contact returns on its next
advert.
The builder panel now labels its actions, lets the user pick round trip
or as-entered with an explanation, and only sends when "Run path trace"
is pressed. Hops, mode and the last result are kept in UiViewStateService
for the session, so going back no longer clears them and the last result
can be reopened without sending again.
Each nearby repeater is now a tappable row that opens the same node
details sheet as the map, or a short sheet with the key prefix and
signal when the repeater isn't a known contact. The map's node info
sheet and login dialogs move to widgets/node_info_sheet.dart so both
places share them.
Notification bodies now use the chat's parsers to show a localized
summary for shared locations (m: markers), channel images, GIFs and
reactions instead of the raw payload. The marker parser moves out of the
map screen into helpers/marker_message.dart so the service can use it.
Drop the row of activity/type/group chips under the Local/Online/Both
switch; every option is already in the filter sheet, whose button now
shows a badge with the number of active filters. Add a one-line hint to
each map source segment.
Contacts now show the first path-hash-width bytes of their public key as
a monospace badge before the path label, so they can be matched to hops
in routing paths and told apart. The width follows the radio's path hash
size setting.
- Detect mentions on the original text, as @[name] or a whole-word @name
- Save and restore the full mode map in review mode
- Open the mode picker from the chat bell and show the mode in its tooltip
- Share one mode picker sheet; fix the stale sheet context
- Persist modes by name and skip unknown entries
- Keep writing muted_channels so older builds keep the user's mutes
- Remove the muteChannel/unmuteChannel/isChannelMuted shims
- Update notifications docs to match the behaviour
- Presets no longer reset the path hash size; the unused preset field is gone
- Confirm the new path hash size from the refreshed DEVICE_INFO and show a
specific error when the radio does not apply it
- Log path hash size with the other radio settings and on manual edits
- Add MeshCoreConnector.supportsPathHashMode and use it in both screens
- Use the same 0-2 mode values and helper text as the other selectors
- Add channels_notifyAll, channels_notifyMentionsOnly, channels_notifyNone to all 18 language ARB files
- Add channels_notificationSettings to all ARB files for consistency (was missing in 16 languages)
- Remove redundant "(@)" suffix from mentions only mode
- All translations verified for accuracy
- Special fix: Slovak "Iba spomienky" -> "Iba zmienky" (mentions, not memories)
- Update all localization Dart files via flutter gen-l10n
- Update documentation table with proper icons
- Update untranslated.json
- Add ChannelNotificationMode enum with all, mentionsOnly, muted options
- Replace mutedChannels Set with channelNotificationModes Map for per-channel settings
- Add mention detection for @username in channel messages
- Update channels list and chat UI with notification mode selector
- Add localization strings for new notification modes
- Automatic migration from old mutedChannels to new system
- Update user documentation
- Preserve backward compatibility with existing mute/unmute API
Fill in untranslated strings for the 17 non-English locales (notification
replies, region settings, channel min-hops, image messages, map clustering,
and more). untranslated.json is now empty.
- Message notifications use Android MessagingStyle with Reply, Mark as read,
and Mute channel actions, so they work in Android Auto and on watches
- Replies go through the normal send path (length limits, SMAZ, Cyr2Lat,
retries), split into up to 3 messages, and report failures
- Declare Android Auto notification support and register the action receiver
- Add a bell icon to channel chat to mute/unmute; unify the channel mute key
so unnamed channels mute correctly
- Update README and docs for Android Auto support
Documentation:
- Correct web transport support: USB via Web Serial in Chrome only; no
BLE or TCP in the browser.
- Fix region scope semantics, routing modes (Auto/Flood/Manual), the
156-byte DM limit, repeater CLI framing, the guessed-location algorithm,
radio stats contents and settings labels.
- Add regions, image messages, radio statistics and troubleshooting guides.
- Restore coding conventions, localization workflow, storage scoping and
transport entry points to CLAUDE.md/AGENTS.md; align build/CI commands.
- Replace the obsolete docs/BLE_PROTOCOL.md with a pointer to the
maintained protocol reference.
Dutch (nl):
- Translate the 79 missing strings and correct existing mistranslations,
typos and grammar (e.g. "Uitzoomen", "Handmatig", "Slowaaks", frequency
range 150-2500 MHz).
- Use consistent terminology and informal "je" throughout; keep mesh terms
such as repeater, node, flood, hop and advert in English.
Fixes#538
- Updated LoRa airtime calculations in `lora_airtime_test.dart` to reflect new reference values.
- Introduced new tests for LDRO behavior and preamble symbol calculations.
- Added `contact_path_width_test.dart` to validate path hash width handling in contacts.
- Enhanced `model_changes_test.dart` to ensure legacy data migration works correctly.
- Created `remote_node_stats_test.dart` to decode and validate remote node statistics.
- Implemented `map_marker_parse_test.dart` for parsing marker text with coordinate validation.
- Developed `map_tile_cache_key_test.dart` to ensure API keys are excluded from cache keys.
- Added `message_retry_failure_test.dart` to test message retry service behavior on failures.
- Extended `path_history_service_test.dart` to preserve learned state across path attempts.
- Enhanced `received_image_store_test.dart` to handle concurrent writes and review fixes.
- Implemented `repeater_command_service_test.dart` to validate command response handling.
- Created `store_tolerant_parsing_test.dart` to ensure stores skip malformed records gracefully.
- Cleared untranslated JSON file for localization updates.
Contacts could only be imported by pasting `meshcore://<hex advert>` from
the clipboard, so contact QR codes and links shared by the official app
(`meshcore://contact/add?name=...&public_key=...&type=...`) could not be
used at all.
Add a contact QR scanner screen, reachable from the contacts menu, that
scans with the camera or decodes a QR code from a photo in the gallery.
Both the official contact-card link and the existing hex advert form are
accepted; cards are applied with CMD_ADD_UPDATE_CONTACT and advert blobs
keep using CMD_IMPORT_CONTACT.
Fixes#529
The device info card truncated the node's public key to its first 16 hex
characters with no way to reveal or copy the rest, so the only way to
obtain it was exporting the advert packet to the clipboard and slicing
the first 32 bytes out by hand, or running `get public.key` over a
serial CLI.
Show the full 64-character key and copy it to the clipboard on tap. The
truncation protected nothing: the on-air identity hash is a single byte
of the same key, and the value was already rendered unredacted.
In channel chat screen, clicking a reaction emoji brings up a popup
listing the received emoji reactions and their senders.
Also fixes a bug that prevented displaying the count numbers on
reactions. Code existed to display counts for multiples, but the
deduplication failed to differentiate between senders and was tossing
them out.
There is still another preexisting bug, not fixed by this commit, that
over-counts sent reactions in rooms.
This adds a simple UI in repeater management settings for remotely
setting a repeater's private key. A key can be pasted from an external
key generator, or a random one can be generated here, optionally with a
specified prefix.
If a prefix is specified, searching is done in 30ms batches in order
to keep the UI responsive and show the progress indicator animation
smoothly. Searches can be interrupted. An estimation of search length is
given as expected number of generated key pairs. (A future improvement
would be to observe keys per second performance and give time estimates
based on that.)
When it generates a new private key on your behalf, it can tell you
what the corresponding public key will be. Unfortunately, if you paste
one in from another source, it can't compute the corresponding public
key. This is because the standard Dart crypto library doesn't provide
that capability, nor does it give access to the elliptic curve functions
it implements so we could do it ourselves. Our only recourse would be to
copy the source for all those things, and I didn't think it was worth
it.
This will not check the validity of a pasted key, but the remote
repeater will. It does limit it to the correct length and hexadecimal
charset.
Prefixes are limited to 4 characters. There's no technical reason for
this, but users are unlikely to want more, and I think it would just be
a bad experience to allow more and spin for a very long time. If someone
really wants a longer one, they can use an external generator like they
do now.
Possible TODO: rewrite background processing using isolates.
Closes#142.