Your browser is the infrastructure.
Reticulum Web v2 turns every tab into a full Transport Node + Propagation Node + WebRTC mesh + RNode LoRa gateway. No servers, no accounts, no ISP lock-in. Messages hop browser-to-browser via WebRTC, or via LoRa when the internet is gone.
🌐 Browser = Router
Transport-enabled: forwards announces, builds path table, grows mesh diameter. Like Tor, but offline-first.
📦 Prop = Mailbox
Stores encrypted LXMF for offline peers. 512 MB pooled storage per node, syncs via Resource protocol.
📡 RNode LoRa
WebSerial → RNode. SF 7-12, 868/915 MHz, -120 dBm. Works when cell towers are jammed or down.
🔗 WebRTC Mesh
Zero-config P2P inside your city without internet. Signaling via local discovery + QR.
How it works — post-ISP comms
🧑💻 Your BrowserTransport + Prop
↕ WebRTC mesh (local) or WebSocket (global)
🌐 70+ Browser Nodes Worldwide● live
↕ Announce propagation • Path cost 2-24
📡 RNode LoRa Gateways868/915 MHz
↔📦 Offline MailboxLXMF store
No central tracker. No IPFS pinning service. Each browser seeds transport table + prop storage. If 3 nodes remain online anywhere, messages eventually deliver via Resource sync.
Why this map matters:
Centralized messengers die when DNS/ISP dies. Reticulum survives because routing lives in browsers + LoRa. This map visualizes that the mesh is already global. Run a node → you add one more purple pin that stores messages for Nairobi when its uplink is cut.