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 meshcore_connector.dart,
Initialize _processedContactReactions in outgoing reactions for DMs
In channel_message_store.dart & message_store.dart,
Handle reaction lists properly to un-break message loading.
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.
Terminate a search for a repeater key with a specified prefix if the
user navigates away from the settings screen.
This commit also adds dispose() calls for the new repeater key input
controllers, which were previously omitted.
- Created a new ExportOptions.plist file to define export settings for app distribution.
- Configured the plist with method, team ID, signing style, symbol upload option, and destination.
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.