Dear fedizens

I'm getting into secure resilient decentralised mesh p2p/p4p communication networks.
(Wow, that's a mouthful)

Could y'all give me some advice about relevant tech and hardware?

My primary use case is getting a few thousand people securely connected (messaging, preferably some web services as well) in a large area (hundreds of km²) with rugged terrain.
Eventually the use case will become fairly similar to "neighbourhood-first software", with 100k people across a few thousand km²: https://tv.lumbung.space/w/nzuB248U2LQA1LCn7vYmER

I've watched and read some stuff about #meshtastic, #meshcore and #reticulum, like
this blog post https://www.jonaharagon.com/posts/im-getting-into-mesh-networks-meshtastic-meshcore-and-reticulum
this glorious video https://www.youtube.com/watch?v=W_F4rEaRduk
and #p4panda in this blog post https://lores.tech/blog/example-chat-app/

I'm leaning in favour of reticulum with p4panda on top, but can be convinced otherwise.

What sorta hardware is suitable?
Is #microreticulum functional?
Do you know of any decent guides?

Boosts welcome, cheers!

#fedihelp #fediask #mesh #networking #p2p #p4p #anarchism #digitalAutonomy #localResilienceTech #decentralization #decentralisation #neighbourhoodFirstSoftware

Debugging #microReticulum LINK/transport behavior over LoRa is hard when the “wire” is invisible.

I’m testing BOB, CY & DAN, with DAN acting as the middle node between two units that cannot hear each other directly. To look for possible RF collisions, I modified #OpenWebRX.

It is fuzzy, but it turns millisecond logs and invisible transmissions into something I can actually see.

https://salemdata.net/johnpress/?p=868

#Reticulum #TBeamSupreme #LoRa #ESP32 #EmbeddedSystems #Radio #SDR #OpenSource #AIcoding

Looking at two Rust paths toward #Reticulum: Reticulum-rs, a smaller MIT-licensed library, and Leviculum, a much broader AGPL implementation with a no_std core, daemon/CLI, interop tests, and embedded ambitions.

My practical question: could either help with #ESP32 / #TBeamSupreme transport work, or does #microReticulum still win today?

https://salemdata.net/johnpress/?p=850

#Rust #EmbeddedSystems #LoRa #NoStd #ProtocolDesign

Herding T-Beam Cats: my practical test bench for running 7 LilyGo T-Beam SUPREMEs with PlatformIO, synchronized clocks, serial monitors, structured logs, and Codex-assisted debugging bounded by actual evidence.

https://salemdata.net/johnpress/?p=777

#TBeamSupreme #ESP32 #PlatformIO #Reticulum #microReticulum #EmbeddedSystems #Gentoo #AIcoding #Codex #HardwareHacking

Two $17 Raspberry Pi Zero 2 W boards exchanging encrypted poems over #Reticulum using Bluetooth only -- no LoRa hat, no extra radio, no carrier network.

A small-board demo of #microReticulum in C++ with BLE as the link layer. Cheap hardware, built-in radios, real packets, real timing, real tinkering.

https://salemdata.net/johnpress/?p=720

#RaspberryPi #PiZero2W #Bluetooth #BLE #Linux #SBC #Maker #SmallBoardComputers

Milestone: Torlando’s Python BLE Reticulum protocol behavior has now been partially distilled into a C++ protocol/session core and field-tested between two Raspberry Pi Zero 2Ws. The test moved the full U.S. Constitution both directions over Reticulum using BLE, with C++ fragmentation/session backends confirmed.

https://salemdata.net/johnpress/?p=695

Next stop: microReticulum on the LilyGO T-Beam SUPREME.

#Reticulum #BLE #Bluetooth #microReticulum #TBeamSupreme #LilyGO #RaspberryPi #ESP32 #LoRa #Cplusplus