[Feature wish] add heard replies, delivery status, retry count and hops to sent and received messages in the chat view (and not only the message details). #241

New Issue

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

adam commented

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

Ahoj,

I would find the following very useful in everyday usage:

In chat overviews (both channels and DMs), i.e. in the screen where several messages of a chat are displayes with timestamp, display directly in the chat view and not only in the details view the number of heard repeats.
Additionally, in DMs and room server messages (i.e. everything where an ACK is expected), display:
- Weather an ACK was retrieved or not,
- current number of retries,
- current path setting (flood/ x hops).

Suggestion for layout:
At the right edge of the last line of a sent message (and make sure that line length might be influenced by that; if needed, wrap line/ display on next line if there is no space), display:

For sent channel messages:
<x>r
where <x> is the number of heard repeats. Colour: Different than message text, e.g. blue or same as timestamp?
For sent direct messages/ room messages:
- if status "pending":
 <x>r <n>/<m> ⌛ 
- if status is "deliverd":
 <x>r <n>/<m> ✓ 
- if status is "not delivered:
 <x>r <n>/<m> ❌ 
where
- <x> is the number of heard repeats,
- <n> is the current try,
- <m> is the maximum number of tries,
-  is a path identifier, one of <y>H for <y> hops or F for flood -- updating when it changes during sending/ tries/ ACK receival for current message (but not changing afterwards).
Instead of ⌛, ✓ and ❌, other, ASCII, characters or self-drawn little symbols could be used, or omit it to save 2 characters space and use colour coding:
- For "pending": blue or mid-yellow (whatever you think is better; blue is already present in the UI so less "colour-clutter"),
- for "delivered": green (mid-green, neither dark nor bright),
- for "not delivered": red (not dark red).

I know this from some apps and also the Ripple firmware and for everyday usage this made thinks much smoother.

Additionally, it could also be nice to have for received messages a <y>H badge -- but I find this less important than the information for sent messages.

Everything as space-saving as possible, no big borders, only space of width of one character or maybe |, and distinguish from the message by colour.

Regards!

Ahoj, I would find the following _very_ useful in everyday usage: * In chat overviews (both channels and DMs), i.e. in the screen where several messages of a chat are displayes with timestamp, display directly in the chat view and not only in the details view the number of heard repeats. * Additionally, in DMs and room server messages (i.e. everything where an ACK is expected), display: - Weather an ACK was retrieved or not, - current number of retries, - current path setting (flood/ x hops). Suggestion for layout: At the right edge of the last line of a sent message (and make sure that line length might be influenced by that; if needed, wrap line/ display on next line if there is no space), display: * For sent channel messages: `<x>r` where `<x>` is the number of heard repeats. Colour: Different than message text, e.g. blue or same as timestamp? * For sent direct messages/ room messages: - if status "pending": `<x>r <n>/<m> ⌛ ` - if status is "deliverd": `<x>r <n>/<m> ✓ ` - if status is "not delivered: `<x>r <n>/<m> ❌ ` where - `<x>` is the number of heard repeats, - `<n>` is the current try, - `<m>` is the maximum number of tries, - `` is a path identifier, one of `<y>H` for `<y>` hops or `F` for flood -- updating when it changes during sending/ tries/ ACK receival for _current_ message (but not changing afterwards). Instead of `⌛`, `✓` and `❌`, other, ASCII, characters or self-drawn little symbols could be used, or omit it to save 2 characters space and use colour coding: - For "pending": blue or mid-yellow (whatever you think is better; blue is already present in the UI so less "colour-clutter"), - for "delivered": green (mid-green, neither dark nor bright), - for "not delivered": red (not dark red). I know this from some apps and also the Ripple firmware and for everyday usage this made thinks much smoother. Additionally, it could also be nice to have for received messages a `<y>H` badge -- but I find this less important than the information for sent messages. Everything as space-saving as possible, no big borders, only space of width of one character or maybe `|`, and distinguish from the message by colour. Regards!

adam commented

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

implemented in v0.9.15

Delivery, route and repeat badges in the chat view (#241): [ok] / [..] / [x], retries, flood / direct / hops and heard repeats, on the device and in the WebUI.

I think this can be more improved but lets give it a try.

## implemented in v0.9.15 **Delivery, route and repeat badges in the chat view (#241):** `[ok]` / `[..]` / `[x]`, retries, flood / direct / hops and heard repeats, on the device and in the WebUI. I think this can be more improved but lets give it a try.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#241