Recent searches
Search options
Wait a minute, wait a minute…
Why is #Meshtastic using MQTT for inter-mesh backhauls instead of, well, #Veilid?
Imagine that not only wasn't there a central server, but there wasn't truly *any* server, and that the more nodes came online, the better it all worked instead of the worse.
100% crypto backend, none of this "should I or shouldn't I use TLS?” stuff. Native JSON API. The radios are too lightweight to run Veilid themselves, but they could talk to a Veilid node as easily as MQTT.
@tek Um, maybe because meshtastic was relatively mature even before veilid was conceived as an idea?
Besides, it’s an open source project and you are welcome to propose veilid support or even try to implement it :)
@lazybitfield@mastodon.world (I wasn’t actually asking as a question to be answered.)
@tek Fair enough. And I agree that having more backends, especially decentralized ones, would benefit meshtastic a lot.
@lazybitfield It seems doable to make a proxy that speaks MQTT in front and Veilid in back. I might have to check that out.
@tek Yeah, was just thinking about this.
For MQTT a wifi access point is enought to connect separate meshtastic segments. But not for veilid right now, or maybe ever.
On a related note: I wish that meshtastic would merge with reticulum, as the former has greater hardware support and is more user-friendly, and the latter is leagues ahead of meshtastic in terms of reliability and various data transports support.