Goal: a DM is either delivered and ACKed, or reported as expired after a configurable retention time, also when the phone is disconnected and when the recipient is only intermittently reachable over many hops (we measured 4-hop round trips at ~32 km working intermittently, and paths of 8 to 12 hops at ~100 km).
Proposal (endpoint-only, no storage on intermediate nodes, in line with the decision in #613):
- The companion keeps unACKed DMs in a persistent outbox in flash, instead of relying on the app to retry while connected.
- Retry policy in the firmware: direct path first, flood with the configured scope after N failures, an immediate retry when an advert or path update from the recipient is received, and backoff otherwise (e.g. 30 s, 2 min, 10 min, 30 min, then hourly) until the retention time expires.
- The recipient dedups on the existing message identity (timestamp + sender), so a lost ACK and a retransmission do not produce a duplicate in the app.
- New companion-protocol push codes for outbox state changes (queued, sent, ACKed, expired), so apps can show delivery state even for messages that were ACKed while the phone was disconnected.
Why in the firmware and not the app: the radio is the always-on device and hears the recipient's adverts. App-side retries stop when the phone sleeps (notably iOS background limits) or disconnects.
Airtime: retries are mostly presence-triggered and backed off, so the flood load should stay below what users generate today by resending manually.
Depends on / related to: #3518 (ACK sent for a DM that is then dropped), #1489 (ACK reliability), #1342 (retransmission of direct messages), #2974 (TX lifecycle signalling).
Happy to discuss the design and help with smaller code changes, but I can't commit to building the full feature.
Goal: a DM is either delivered and ACKed, or reported as expired after a configurable retention time, also when the phone is disconnected and when the recipient is only intermittently reachable over many hops (we measured 4-hop round trips at ~32 km working intermittently, and paths of 8 to 12 hops at ~100 km).
Proposal (endpoint-only, no storage on intermediate nodes, in line with the decision in #613):
Why in the firmware and not the app: the radio is the always-on device and hears the recipient's adverts. App-side retries stop when the phone sleeps (notably iOS background limits) or disconnects.
Airtime: retries are mostly presence-triggered and backed off, so the flood load should stay below what users generate today by resending manually.
Depends on / related to: #3518 (ACK sent for a DM that is then dropped), #1489 (ACK reliability), #1342 (retransmission of direct messages), #2974 (TX lifecycle signalling).
Happy to discuss the design and help with smaller code changes, but I can't commit to building the full feature.