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

Request zero hop advert from repeater (privately or direct)

Aperta
#3,611 10 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
networking

Direzione di ricerca

Start by reading the repeater advert and private messaging flows; the issue does not name files, tests, or entry points, so locate those in the repository. Determine how an advert request should work for direct or private delivery and under guest login, then define and test the behavior for requesting and sharing a repeater advert.

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

Descrizione

While converting over to MeshCore in Evansville, I've been wishing for the ability to request an advert from a repeater.

The default is 47 hours for a flood advert and 0 hours for a zero hop advert.

Let's face it, many new repeaters are put up by those not knowing how important to send a flood advert after setting location and syncing the time. Although an advert is not needed for repeating traffic or public messages, for those (including the new user) wanting to set routes, private message won't be able too until after the advert. This also delays creating neighbors and map visibility for days or at least until the advert is sent and heard. And if there is no observer, or no one to add it to the internet map after receiving the advert then it is further delayed.

It is necessary to receive an advert to share a contact to the internet map or to share via zero hop advert. For new repeaters that are not connected to my observer, the only option is to drive to that repeater and wait and hope to get an advert so I can share it with my observer later via a zero hop advert.

Today I asked a friend to change his repeater id due to a conflict with an anonymous repeater that didn't care they took his id. With no contact info for the new repeater, I had to ask my friend to change his id. He is only connected to one other repeater and not the rest of town (we are working on it). No one got the advert. If only, I could request an advert to me like a private message. Or under the guest login, I could request a zero hop advert be sent out. Then I can add him to the map and meshmapper, let's mesh and my meshcore server. At this point my option is to sit for two days or drop off a companion to wait the two days.

This seems to be a design flaw. Requesting a private message advert would be perfect.

Thanks!

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.