Decentralized networking resurfaces with Reticulum mesh protocol
Reticulum, a decentralized mesh networking protocol that deliberately omits source addresses from packets, got attention in a thread today. The project is designed to work over LoRa, radio, and other low-bandwidth links, and explicitly aims to make surveillance by traffic analysis harder. Comments compared it to concepts from Neal Stephenson's Anathem and noted the similarities to MeshCore.
This is a small but recurring signal on HN: interest in infrastructure that doesn't depend on central providers and doesn't leak metadata by design. It shows up in the same week as the Cloudflare analytics injection story and the Flock camera discussion, which is probably not a coincidence. The appetite for infrastructure that you actually control is growing.
The counterpoint: anonymizing the source address solves one problem but creates others, including making abuse harder to trace. The thread flagged this limitation directly.
So what?
Reticulum is niche today, but the underlying demand it represents is not. If your product depends on centralized infrastructure for features that users increasingly want to control themselves, the gap between what you offer and what a privacy-conscious user wants is growing. Worth watching whether projects like this gain developer traction the way Tailscale did, by solving a real pain point with a usable implementation.