Request zero hop advert from repeater (privately or direct)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- c
- Área
- networking
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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!
- Lenguaje dominante
- C
- Estrellas
- 3.9k
- Forks
- 1.5k
- Merge medio
- 19 h 9 min
- PR fusionados (30 d)
- 27
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de meshcore-dev/MeshCore
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
meshcore-dev/MeshCore#3622 ·
Los mantenedores suelen responder en 1 día
-
[Feature Request] Set Australia (Mid) Preset to automatically enable 2 byte default path hash sizeAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
meshcore-dev/MeshCore#3571 · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
meshcore-dev/MeshCore#3567 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
RTC_RX8130CE writes and reads the one-hot WEEK register as a numberPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
meshcore-dev/MeshCore#3549 ·
Los mantenedores suelen responder en 1 día
-
Repeater: CLI reply to 'setperm <key> 0' is lost when the removed ACL entry sits before the requester (stale ClientInfo* after array shift)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
meshcore-dev/MeshCore#3513 ·
Los mantenedores suelen responder en 1 día
Todos los issues de meshcore-dev/MeshCore
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
quickjs-ng/quickjs#1836 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
open-quantum-safe/liboqs#2637 ·
Los mantenedores suelen responder en 1 día
-
Go device SDK: Whisper transcriber keeps buffering and transcribing audio appended after Stop()Posiblemente ocupada @apoorvdarshan la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
BasedHardware/omi#22770 ·
Los mantenedores suelen responder en 1 día
-
fido_do_ecdh() reports any getKeyAgreement failure as FIDO_ERR_INTERNALPosiblemente ocupada @brlumen la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
joncampbell123/dosbox-x#6698 ·
Los mantenedores suelen responder en 1 día