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 "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."
Sounds like I2P. Why is Veilid reinventing I2P?
@timlocke It’s not.
@tek Useless comment. I've been trying to find out what's different since it was announced and no one knows.
@timlocke Your comment wasn’t completely useless. It was unasked for, phrased insultingly, and begging the question (while being wrong), but there was a nugget of use in there.
One big difference is that Veilid is designed as a library, not a service. Link it into your app, make some API calls, and now your app is Veilid-native. While lots of people run Veilid nodes today, they’re basically a thin wrapper around the library use to help bootstrap the mesh.