Thanks. Found it here. Interesting choice to make. I would need offline mesh as a transit layer, so either will do. It's closer to the vision of reticulum. But the fastest path would be to bootstrap off existing mesh. I will look at how widespread is reticulum. Meshtastic seems to be firing right now. https://blog.erethon.com/blog/2024/01/31/comparing-reticulum-and-meshtastic/
you can do more with reticulum. you can even run VPN/ssh through it, it has propagation nodes for offline distribution of messages (amazing for ecash), it works over any medium, not just Lora - wifi halow, Ethernet, lxmf (the messaging) works even over qr codes.
simple hypertext pages,...
the main advantage of meshtastic is that ESP32 is enough for routing node.
Really cool. It seems like we could even run a full nostr client over reticulum (for users and DMs at least, maybe needing to be mindful of bandwidth for other uses). Now I wonder about building apps on reticulum, which on daily use work in an internet connected way, but in Internet-down scenarios, can use this other networking stack to failback; for example to a local mesh...
that's very easy to do. check lxmf proxy in nutband.
since reticulum is medium agnostic, you can just run it over reticulum all the time and it will fall back to Lora automatically when wifi gateway does not work.
but what would be good is to create a small language model as a mean of compression for the public notes.
