Panda_

share a single secret to become that specific closed network

No? Pretty sure that isn't true.

You get an address by creating a random private key public key combination (no collisions are ensured by entropy).

You then send an announce packet over all the connections to other nodes you have. This packet tells everyone else how to reach you and that you exist. To send packets to you they send to the connection they got your announce came from, then the node on the other end of that connection sends to where it got the announce from and so on until it reaches the origin node where the destination must be.

The manual at https://reticulum.network/manual/index.html is the best source of information on Reticulum but it isn't very beginner friendly.

Reticulum uses AES-256 encryption, which is considered quantum safe due to the sheer number of extra combinations adding 128 bits to AES 128 creates, including by NIST[1].

It uses AES because AES is extremely well tested and vulnerabilities have not been found.

The new quantum safe algorithms are still mostly in beta and a few have already been broken. They also have extremely large key lengths which breaks the fundamental idea of Reticulum being able to run over any almost any connection, including LoRa. See what the creator of Reticulum said on the topic [2].

[1] https://csrc.nist.gov/projects/post-quantum-cryptography/faq... "To protect against the threat of quantum computers, should we double the key length for AES now? (added 11/18/18)"

[2] https://github.com/markqvist/Reticulum/discussions/181#discu...

The ending notes about a mesh network remind me of the Reticulum Network Stack[1].

As far as I can tell, RNS is a networking protocol that attempts to provide a mesh network that can run over almost any bidirectional connection (and interconnect different types of connections) without centralisation (basically random addresses using encryption, and announces to make that address reachable).

It's kinda similar to Meshtastic and Meshcore but designed to be more generic for any connection. Compared to Meshcore it's less bandwidth efficient since it uses larger addresses but I like RNS more because it's more generic (it's intended to be fairly bandwidth efficient but at a larger more internet level scale than just kilobytes per second) and less proprietary than the Meshcore official ecosystem. Compared to Meshtastic, RNS is much more efficient since it doesn't use flood routing for every packet.

[1] https://reticulum.network/

Reticulum would probably be the best one for it. As far as I can tell there aren't any interfaces for it already, but if you can get a command that transfers data using stdin and sdtout, Reticulum has things like the PipeInterface https://reticulum.network/manual/interfaces.html

Saw this at https://discuss.privacyguides.net/t/im-getting-into-mesh-net... and thought it was interesting

The Reticulum Network Stack is a more generic lora capable protocol. It is intended to run over almost any two way link so it's less bandwidth efficient per packet than Meshtastic but in return it gives you packet routing rather than flooding. It can be run over TCP, LoRa, WiFi, etc.

https://reticulum.network/start.html has an overview and how to connect.

There is a manual with a lot more information on how it works and the ideas behind it at https://reticulum.network/manual/ however it's quite large and not really a user friendly guide

If you just want to play with it https://reticulum.network/manual/software.html has a list of clients and software using it.

https://archive.is/5GHWF

Try https://archive.is/5GHWF

Personally I would use something like a Reticulum Network for this kind of thing with a simple Python script to establish a Link between the two devices and send a Resource.

I still use it on a couple of devices where I haven't been bothered to change the default. On devices I use a lot, I normally use Duckduckgo or Ecosia

Interesting... Looks like it would be good for RAG. Maybe add Ollama support for local hosting?