Great to see yet another project to provide "offline"-ish comms.
The existing solutions are obviously not good enough yet, hence why all these projects are popping up. I hope we get to a good-enough one soon.
LoRa is great, but the bandwidth is terrible, so you'd be limited to Twitter sized messages when using this comms channel.
ews 4 hours ago [-]
has anyone used reticulum and how does it compare to meshtastic (or even meshcore?)
montyanne 4 hours ago [-]
Reticulum is a full replacement networking stack for several layers of the OSI stack, so not directly comparable. The LXMF messaging protocol (built on top of reticulum) is nice as it’s encrypted-by-requirement, but doesn’t really have a ton of non-text messaging implementations.
Reticulum is not worth getting into, the utilities and general infrastructure just isn’t there yet.
The project was basically a one-man-show for a long time, and has a lot of odd, esoteric decisions that will drive you mad if you’re actually trying to build something with it (eg, configuration files with sparse documentation that are yaml-but-not-really). I don’t mean to belittle the loads of time the original maintainer put into this project, it’s just not really designed to be usable in the general case by other developers.
I spent some time porting the reference Python implementation to no_std rust, but basically had to roll all the basic debugging utilities myself.
bzb 3 hours ago [-]
I’ve been looking at that exact project to bolster my embedded Rust. Is your implementation available for review? Thanks!
montyanne 1 hours ago [-]
I was using this as a demo project for playing around with code generation tools, so it’s really not in a great state and entirely AI written, but I can share a link here when I get a chance.
My initial stab was a rust port targeting esp32 Heltec V4 (since it has some niceties like tokio) with Reticulum communication over serial, BLE, WiFi and LoRA. The serial interface was sort of working, but frankly debugging using rnsd/nomadnet was infuriating (there’s no tools just to easily see messages over the wire!).
I’ve moved onto a build system that can also target the SEEED Wio Tracker using no_std, but it’s been… messier. AI tooling doesn’t quite have the context length for big migrations like that yet.
31337Logic 2 hours ago [-]
Interesting project, thanks!
Seems a little complicated though? How do I set this to communicate over only TCP or Bluetooth? I think that's a common use case (where no Internet is available) yet it seems unnecessarily complex to activate.
zacklee-aud 4 hours ago [-]
[dead]
Rendered at 05:54:26 GMT+0000 (Coordinated Universal Time) with Vercel.
LoRa is great, but the bandwidth is terrible, so you'd be limited to Twitter sized messages when using this comms channel.
Reticulum is not worth getting into, the utilities and general infrastructure just isn’t there yet.
The project was basically a one-man-show for a long time, and has a lot of odd, esoteric decisions that will drive you mad if you’re actually trying to build something with it (eg, configuration files with sparse documentation that are yaml-but-not-really). I don’t mean to belittle the loads of time the original maintainer put into this project, it’s just not really designed to be usable in the general case by other developers.
I spent some time porting the reference Python implementation to no_std rust, but basically had to roll all the basic debugging utilities myself.
My initial stab was a rust port targeting esp32 Heltec V4 (since it has some niceties like tokio) with Reticulum communication over serial, BLE, WiFi and LoRA. The serial interface was sort of working, but frankly debugging using rnsd/nomadnet was infuriating (there’s no tools just to easily see messages over the wire!).
I’ve moved onto a build system that can also target the SEEED Wio Tracker using no_std, but it’s been… messier. AI tooling doesn’t quite have the context length for big migrations like that yet.