[INVALID] Heard repeats: Not all repeaters are shown with full name, although contacts exist (and exist only once). #249

New Issue

2026-10-27T15:45:51+01:00

adam commented

2026-10-27 15:45:51 +01:00

Describe the bug

When I view the details of a sent message (in this case, a channel message), in the Repeats: section, some repeater hashes are expanded to full names as known by the contact list, others are not although contacts exist.

Specifically:

I currently have a message where the Repeats: section shows:

Repeats:
1) r_____l [5E]
2) D_____P [51]
3) -- (3) [2B]
4) -- (2) [90]
5) -- (2) [75]

(the _ are a bunch censored characters which I have removed by hand.)

When I look up the hashes (public key prefixes) in the contacts list in a connected companion app, I find for the hashes above contacts (one or more):

[5E]: 1 Contact, r_____l.
[51]: 1 Contact, D_____P.
[2B]: 1 Contact, F_____n.
[90]: 2 Contacts, D_____r and 6_____L.
[75]: 1 Contact, D_____L.

I would expect that all hashes are replaced by names when there is exactly one matching contact in the contacts list, which is the case for all except [90], so especially also [2B] and [75].

When there are more than one matching contacts, it would be helpflul ([Feature wish]) to display some information about that and reveal all matching repeaters when tapping on the information:
E.g. display 4) D_/6_ (2) [90] (where D_ and 6_ are the first very few characters of the matching contacts; maybe coloured differently?) and on tap show a selection dialogue if #234 is to be implented for "heard repeats" view.

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.12

Regards!

**Describe the bug** When I view the details of a sent message (in this case, a channel message), in the `Repeats:` section, some repeater hashes are expanded to full names as known by the contact list, others are not although contacts exist. Specifically: I currently have a message where the `Repeats:` section shows: ``` Repeats: 1) r_____l [5E] 2) D_____P [51] 3) -- (3) [2B] 4) -- (2) [90] 5) -- (2) [75] ``` *(the `_` are a bunch censored characters which I have removed by hand.)* When I look up the hashes (public key prefixes) in the contacts list in a connected companion app, I find for the hashes above contacts (one or more): * `[5E]`: 1 Contact, `r_____l`. * `[51]`: 1 Contact, `D_____P`. * `[2B]`: 1 Contact, `F_____n`. * `[90]`: 2 Contacts, `D_____r` and `6_____L`. * `[75]`: 1 Contact, `D_____L`. I would expect that _all_ hashes are replaced by names when there is exactly one matching contact in the contacts list, which is the case for all except `[90]`, so especially also `[2B]` and `[75]`. When there are more than one matching contacts, it would be helpflul (\[Feature wish\]) to display some information about that and reveal all matching repeaters when tapping on the information: E.g. display `4) D_/6_ (2) [90]` (where `D_` and `6_` are the first very few characters of the matching contacts; maybe coloured differently?) and on tap show a selection dialogue if #234 is to be implented for "heard repeats" view. **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.12 Regards!

adam closed this issue

2026-10-27 15:45:51 +01:00

adam commented

2026-10-27 15:45:52 +01:00

Closing due to having been confused. About to open a correct one: → #250.

Closing due to having been confused. About to open a correct one: → [#250](https://github.com/dabeani/meshcoreterm/issues/250).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#249