It works over TCP too. No need for radio hijinx.

So you basically eliminate futzing around with the hard parts until you understand the reticulum network itself.

Basically work your way down the OSI model instead of working your way up it.

because the protocol is transport agnostic, there are a lot of interfaces to the public reticulum net that you can access over TCP, I2P, or yggdrasil.

https://github.com/markqvist/Reticulum/wiki/Community-Node-L...

takes away some of the fun of imagining the SHTF-all-corporate-infrastructure-is-gone scenario i guess but i think that for realistic mesh networking applications it’s cool to build out many infrastructure types and enjoy the fact that the mesh will reconfigure itself realtime across a variety of scenarios.

Perhaps there are others in your neighborhood in the same position, who would only get into it if there were other nodes. So be the first, get your friends into it, and maybe more nodes will follow. It's only $30 or so for a device.

They have a decent range (15 miles or more) so depending on how rural you are, you might be able to create a line of repeaters back to a major population center.

I ended up getting a ham radio license and now I get to use technology that actually works (even if it's a little more janky than meshtastic/reticulum).

My friend is across town and I should be able to hit him with the line of sight meshtastic repeater from my house, but I've never been able to.

OTOH, we can hear each other clear on any of the ham bands.