I've been spending time researching, building, and testing different resilient and mesh type networks and hardware. I started playing with #Meshtastic but keep getting pulled towards #Reticulum network and #RNodes. Meshtastic has the marketing, ease of entry, and hardware support. In actual execution it suffers the same downsides as FMRS radios. Reticulum is something much more. A complete encryption first network stack capable of leveraging the best path whether that's across the internet, across ISM band or other radio links or both. The ability to cache messages in the network until a node becomes available again, and no arbitrary three hop limit is a plus. Being able to text with someone out of eyesight through the radio and also with someone on the other side of the globe at the same time is very interesting. What it lacks is the fit, polish, marketing, and momentum of Meshtastic. In every other way, I find it to be superior. Oh, you can also send images, voice messages and files over Reticulum as well. Here is my first Reticulum node running Meshchat on a Raspberry Pi connected to a RAK flashed with RNode all powered with PoE. I'm building a few of these to start building out a local/regional network over time.

Reply to this note

Please Login to reply.

Discussion

#Reticulum has got legs

The ecosystem will get built out over time. It's just a bigger challenge for developers than nostr.

I'm quite interested in using these bots to build apps

https://lxmfy.quad4.io/

nice, ya i keep meaning to try meshcore too..

I was also tempted to try Meshcore. I settled on skipping it for two main reasons. While it seems to solve some of the potential weaknesses found in Meshtastic, it isn't popular or even known in my area. It also doesn't differentiate itself enough from Meshtastic. Reticulum, with caching, routing, and the ability to use basically any type of wired or wireless network and make them interoperable doesn't have the same limitations. It has different ones currently, but Reticulum looks like a solid base to build something from.

Why can't Reticulum use Meshtastic as a transport layer?

It can, there is a github project that enables that. I've not tested it yet. The additional features that I have using RNodes over Meshtastic devices has kept me from trying this out. I will test it eventually.

I take it the github project is some offshoot of reticulum and not the official project?

I didn't see that feature in the mobile app and the only tranport layers I see in the documentation is LoRa and IP networks.

https://reticulum.network/manual/networks.html

I'd expect if they could use Meshtastic, they would be very quick to mention that since the Meshtastic network is already so strong.

This is a project that I've looked at that enables a Meshtastic interface in Reticulum. https://github.com/landandair/RNS_Over_Meshtastic