For nearly a decade, Mark Qvist built something remarkable, alone, and gave it away for free. Here's what happened after he walked away.
Before we get into what just happened in the mesh networking world, let me tell you about a guy named Mark Qvist.
For nearly a decade, working mostly alone, Qvist built something that most people in the technology world have never heard of. He called it Reticulum. The simplest way to describe it is this: imagine someone rewrote the foundational rules of the internet from scratch, with one goal in mind. Not speed. Not profit. Not market share. Privacy. Specifically, a kind of communication where nobody — no government, no corporation, no hacker — can intercept what you're saying, trace where it came from, or flip a switch to turn it off.
He built it to run over anything. WiFi, ethernet, satellite, Bluetooth, packet radio, and yes, the same cheap LoRa radios that power Meshtastic nodes. He wrote the protocol, the reference code, the firmware for the radios, the messaging app, the distributed web browser. Nearly everything in the Reticulum ecosystem came from one person, working quietly, publishing his work for free.
Then in December 2025, he walked away.
To understand why this matters, you need to understand what Reticulum actually is versus what most people think it is.
Meshtastic is an application. A complete, self-contained thing. You buy a radio, flash the firmware, pair it to your phone, and you can text people on the mesh. Everything is decided for you. It's brilliant in its simplicity.
Reticulum is something different. It's less like an app and more like a language: a set of rules that any application can be written in. The rules say: every device gets a cryptographic identity, derived from math, that nobody issued and nobody can revoke. Every message is encrypted end-to-end by default, not as a feature you turn on, but as a condition of the protocol existing at all. No source addresses are included in any packet, meaning a message reveals its destination but not where it came from. And it runs over any physical medium that can carry data, no matter how slow or unreliable.
Sideband, the messaging app that runs on top of Reticulum, is built on these rules. NomadNet, the distributed web platform, is built on these rules. Anything someone wants to build — voice calls, file transfer, remote monitoring, community bulletin boards — can be built on these rules.
Qvist dedicated the protocol itself to the public domain in 2016. Nobody owns it. Nobody can take it back. That decision, made years before he walked away, is the reason the story doesn't end with him leaving.
In April 2025, several months before his final withdrawal, Qvist made a change to the license on his code — the reference implementation of Reticulum, the software that actually runs it. He added clauses prohibiting use by AI training systems and requiring that the software not be used for harm.
The intent behind those clauses is understandable. The effect was a problem nobody anticipated.
Major Linux distributions like Debian, which package and distribute thousands of open source programs, have strict rules about the licenses they accept. F-Droid, the app store for open source Android apps, has similar requirements. The new Reticulum license didn't meet those standards. Overnight, Reticulum became ineligible for distribution through the channels that most developers and users rely on to discover and install software. To put that concretely: if a Linux user can't run a single command to install something — if it isn't in their package manager at all — most of them will simply never find it. That's the kind of friction the license change introduced.
The protocol was still in the public domain. The ideas were still free. But the main working version of the code became harder to reach for ordinary users, and harder for developers to build on in certain commercial or institutional contexts.
Then Qvist went quiet. The issue tracker on his GitHub repository, which contained years of technical discussion and community knowledge, was hidden. No new bug reports. No responses to questions. No community management. Development continued — he still pushed code — but the public conversation stopped entirely.
This is the part that doesn't get written about, and it's the part that actually matters.
In February 2026, developers who had been building with and around Reticulum showed up at FOSDEM, the world's largest open source software conference, held annually in Brussels. They filled two sessions. One was a community meetup to work through what had happened and figure out what to do. The other was a technical presentation on porting Reticulum to a new programming language entirely.
The license problem had a straightforward solution. A fork called RetiNet had been created before the license change, meaning it preserved the older, more permissive terms. It's fully compatible with Qvist's version. Devices running RetiNet and devices running the original can communicate without any issues, and it can be distributed through F-Droid and packaged for Linux distributions again. The community now has a version of Reticulum they can distribute freely, maintain openly, and accept contributions to without restriction.
The more ambitious response was the Rust port. The original Reticulum is written in Python, a programming language that is powerful and readable but slow, and particularly rough on mobile phones and small devices. Developers at Beechat Network Systems built a Reticulum implementation in Rust — a language known for running fast with very little memory overhead. A separate project called Leviculum took a similar approach, and by early 2026 had a functionally complete Rust implementation that was tested against the Python original on real hardware and found to be wire-compatible — meaning both versions speak exactly the same language over the air, and a device running one can talk to a device running the other without either knowing the difference.
A Rust implementation that compiles down to tiny, efficient code can eventually run directly on microcontrollers, the same small chips inside a thirty-dollar LoRa radio. Right now, running Reticulum properly requires a separate computer like a Raspberry Pi connected to the radio. If Reticulum can run on the radio itself, the hardware requirements collapse. The barrier to deploying serious, cryptographically sound mesh infrastructure drops considerably.
None of this changes anything about a Meshtastic setup. The two projects coexist and complement each other, and Meshtastic isn't going anywhere. But for anyone who's been curious about Reticulum and found the setup too daunting, the community activity of early 2026 is working directly on that problem: the FOSDEM sessions flagged documentation gaps and new user friction as top priorities, and several people are now building more accessible entry points. And for anyone wondering what the long-term destination of the mesh networking movement looks like, what it grows into beyond group chat and GPS tracking, Reticulum remains the clearest answer available. The community showed up at FOSDEM and started building rather than waiting for one person to return. That's evidence the vision is bigger than any single developer.
Qvist built something designed to outlast its creator. It appears to be doing exactly that.
Mark Qvist spent nearly a decade building tools for human communication that no government can surveil and no corporation can monetize, gave them away for free, and by most accounts burned out. The community that showed up at FOSDEM wasn't there to criticize him. They were there because what he built matters enough to continue.
That's a strange and hopeful thing about open source at its best. The person who starts the fire doesn't have to keep tending it. If the fire is worth keeping, someone usually does.