Replies: 1 comment 1 reply
-
Love it! Haven't dug too deeply into the nuts and bolts, but I'd say both have a broadly similar concept and encryption, The major difference is in the . . . look, I don't mean values in a moral sense, they're highly compatible in that regard, but their values are different in what they believe is important. Veilid remains on TCP and is highly extensible. That's more than fine, it's probably 99% of use cases. Reticulum places less value on doing everything and is a ground-up network stack that highly values efficiency and can run effectively over packet radio. Both have their place, and while I think Veilid may do some thing better than Reticulum, I think Reticulum can handle more use cases. I do like their rapid search algorithms, though, as I strongly believe one of Reticulum's major avenues for improvement is memory usage, and moving the routing tables from RAM to a rapidly searchable file system (with a most-used cache in memory) would make a considerable difference. However, I am not the person to provide a specific suggestion or implement such a system. All in all, I like seeing this kind of thing. More options is good in the short term, and I think the implementations are all young enough that more ideas and testing are more important than interoperability. Since we can all bridge to TCP, I doubt that's too terrible an issue anyway. Could you imagine different network protocols and even physical networks all talking to each other? It's a beautiful mess. |
Beta Was this translation helpful? Give feedback.
-
launched today at DEFCON by the Cult of the Dead Cow. it seems to be trying to solve similar problems and also operates at a low level similar to where Reticulum sits. i thought it worth mentioning and i'm interested to know what you all think of the project and where it differs from Reticulum/NomadNet.
https://veilid.com/Launch-Slides-Veilid.pdf
Beta Was this translation helpful? Give feedback.
All reactions