Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature request] Persistent outbox in the companion: retry direct messages until ACKed

Aperta
  • Qualcosa non va?
#3,519 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
networking

Direzione di ricerca

Start by reading the related issues #3518, #1489, #1342, and #2974, plus the decision in #613, to understand the existing ACK, retransmission, and TX lifecycle behavior. Then locate the companion firmware’s message handling and companion protocol push code. Done means persistent retry and expiry behavior, deduplication, and outbox state updates work across phone disconnections and intermittent multi-hop reachability.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C
Stelle
3.9k
Fork
1.5k
Merge medio
1g 3h
PR unite (30g)
24

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di meshcore-dev/MeshCore

Tutte le issue di meshcore-dev/MeshCore

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.