UI Feat: allow manual resend for unacknowledged DMs #198

New Issue

2026-10-05T02:03:12+02:00

adam commented

2026-10-05 02:03:12 +02:00

It's currently possible to resend group flood messages, e.g. if no repeat was heard.

=> would be nice to be able to do this for DMs as well when there was no ack. I know that there is an auto-resend mechanism for DMs but what if it fails and gives up?

It's currently possible to resend group flood messages, e.g. if no repeat was heard. => would be nice to be able to do this for DMs as well when there was no ack. I know that there is an auto-resend mechanism for DMs but what if it fails and gives up?

adam commented

2026-10-05 02:03:13 +02:00

So we actually do retry in the background -- we try to send three times, and the final time we reset the path and attempt to send as a flood. So it does sort of look like there's not a way to retry, but in reality we've already had three attempts to send, and then we do give up, as a fourth or further attempt is pretty unlikely to result in an ack. I think I would class this as a low priority/wontfix as it's pretty easy to just copy/paste in the unusual case that three attempts is insufficient. I'm open to a counterargument, though! Let me know your thoughts.

So we actually do retry in the background -- we try to send three times, and the final time we reset the path and attempt to send as a flood. So it does sort of look like there's not a way to retry, but in reality we've already had three attempts to send, and then we do give up, as a fourth or further attempt is pretty unlikely to result in an ack. I think I would class this as a low priority/wontfix as it's pretty easy to just copy/paste in the unusual case that three attempts is insufficient. I'm open to a counterargument, though! Let me know your thoughts.

adam commented

2026-10-05 02:03:14 +02:00

Ok, so here are my thoughts: it would be nice to have an indicator that tells the user how many retry attempts are still pending so that he doesn't bother until all of them failed and only by then, manual retry should be offered.

Use case: sometimes even a flood message won't help, e.g. when the recipient keeps moving through a city with areas of bad coverage, e.g. when he's driving in a tram.

Ok, so here are my thoughts: it would be nice to have an indicator that tells the user how many retry attempts are still pending so that he doesn't bother until all of them failed and only by then, manual retry should be offered. Use case: sometimes even a flood message won't help, e.g. when the recipient keeps moving through a city with areas of bad coverage, e.g. when he's driving in a tram.

adam commented

2026-10-05 02:03:14 +02:00

I think part of my hesitancy here is that a missed ack doesn't mean no receipt, and I'd prefer to make resends be explicit actions of the user. I'm going to keep this open to keep the idea turning over, but I think I'm leaning towards leaving this as fully manual for now.

I think part of my hesitancy here is that a missed ack doesn't mean no receipt, and I'd prefer to make resends be explicit actions of the user. I'm going to keep this open to keep the idea turning over, but I think I'm leaning towards leaving this as fully manual for now.

adam commented

2026-10-05 02:03:15 +02:00

Ok, then why not drop existing auto-resend feature in favor of a fully manual resend button (which becomes active only when no ack was received)?

Ok, then why not drop existing auto-resend feature in favor of a fully manual resend button (which becomes active only when no ack was received)?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#198