Using Tailscale as the IP Underlay for Reticulum
Reticulum does not need Tailscale, but its TCP interfaces can use a Tailscale path just like any other private IP network.
mesh
The Hidden Cost of One More Hop in a Mesh Network
An additional route in a mesh is useful, but every extra hop makes the message wait at another point. Receiving, processing, and retransmitting all consume time and resources. More links do not create free capacity.
A Reticulum Interface Is Not the Same Thing as the Internet
One of Reticulum's interesting properties is that communication does not have to be tied to a single medium. But adding an interface does not automatically give every application a conventional Internet connection.
Where Should a Message Wait for an Offline Node?
Communication is simpler if every node is assumed to be continuously available. Real nodes disappear because of power, radio conditions, or the environment. Then the design has to decide where a message waits and how long it remains relevant.