Rendered at 03:24:28 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
xx__yy 24 minutes ago [-]
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 2 hours ago [-]
has anyone used reticulum and how does it compare to meshtastic (or even meshcore?)
montyanne 1 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 11 minutes ago [-]
I’ve been looking at that exact project to bolster my embedded Rust. Is your implementation available for review? Thanks!
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.