> Source: Data Slayer, "The Open Source Internet Is Here" (2026-09-20, ~59 min, million-plus views), video transcript | 8 public sources cross-checked
Bottom line first: this is a hands-on test video. The creator started by receiving 450 LoRa nodes from a Florida highway, earned an amateur radio license within three weeks, and finally used an open-source SDR to bridge a Reticulum message onto an HF ionospheric link, delivering the project before its deadline. Each technical claim checks out: Reticulum really is a transport-agnostic encrypted network stack; Hermes Lite 2 really is open-source hardware covering 0–38.4 MHz (per Hackaday specs); a 1,600-mile FT8 contact is routine HF territory—no exaggeration. The hardest conflict in the video—an encrypted network stack hitting the US amateur radio encryption prohibition—gets only the four words "compliance challenge" in the source material. That is precisely the most informative part, and this piece expands on it.
What the creator actually built
The narrative has three layers. Layer one is the current state: on the 915 MHz license-free band, the creator received 450+ Meshtastic nodes along a highway from central Florida toward New Hampshire (per the video's own measurements)—community networks already form contiguous coverage along population corridors. Layer two is receive-only verification: on 21 MHz, FT8 messages from Bogotá, Colombia (~1,600 miles) and the WWCR shortwave broadcast from Nashville (~727 miles)—ionospheric skywave reflection is a genuinely usable free long-haul link, and receiving requires no license at all. Layer three closes the loop: after earning a Technician license, the creator posted results on Reddit (r/ModernRadio, 09-22)—"an ordinary Reticulum message handed to an HF gateway, transmitted on the 10-meter band (28 MHz), decoded at the far end." The antenna was a nanoVNA-tuned dipole near 28 MHz; the hardware was a Hermes Lite 2 that arrived three weeks earlier and was mounted in an enclosure by hand.
Transport-agnostic: separating the network layer's interface from its implementation
Reticulum is not a radio protocol. It is an encrypted network stack by Mark Qvist—encryption, routing, and identity all happen inside the stack, and what medium runs underneath is up to you: LoRa, WiFi, Ethernet, AX.25 packets, internet tunnels, even "restricted networks that only allow web traffic." d-central's review nails it in one line: Reticulum is not a radio; it is a complete cryptographic networking stack.
This architectural claim should look familiar to readers here: separation of interface and implementation. The medium is swappable and the protocol belongs to the user—in effect, the network layer is pried out of carrier hands and turned into software. Cellular and satellite paths are rented; monthly fees and per-message billing are a continuous interface tax. Reticulum paths are your own, and the tax takes a different shape (explored below).
Four roads to long distance: who collects what tax
| Path | Coverage | Ownership | Form of tax | |---|---|---|---| | Cellular | Base station density | Carriers | Monthly fee | | Satellite (Starlink/Garmin/Iridium) | Global | Proprietary systems | Plans + per-message billing | | Meshtastic mesh | Node density | Users | Participants needed along the route | | HF skywave bridge | Hundreds to thousands of miles per hop | Users + the ionosphere | Time |
For the first two, the tax is money; for the third, it's crowd density—thousand-mile mesh depends on people deploying hardware all along the way. The fourth's tax is time: one FT8 slot is 15 seconds, payloads a dozen-odd bytes. The creator's choice is a combination: local community runs Meshtastic/Reticulum, long distance bridges over HF to connect remote communities—be a gateway, not an island.
The compliance crack: full-stack encryption vs. the no-encryption band
FCC Part 97 (47 CFR §97.113(a)(4)) prohibits encoding "for the purpose of obscuring the meaning." Amateur bands carry a tradition of open monitoring: anyone can decode any transmission. Reticulum's core property is exactly end-to-end encryption and forward secrecy. The two claims collide head-on.
GitHub discussion #399 discusses a hard-edged solution: publish the private keys publicly. Once the key is public, encryption degrades to "authentication without confidentiality"—anyone can read it, but no one can forge it. This is not a hack; it is the standard cryptographic separation of signing from encryption: the amateur band's "no hidden meaning" is satisfied by plaintext plus signature, and confidentiality yields to the monitoring tradition. That line in the source material—"must simultaneously achieve an autonomous path and legal compliance"—is not really a legal question; it is an architecture question.
The community has a second road: one creator demonstrating Reticulum over AX.25 deliberately chose commercial bands rather than amateur bands—commercial bands allow encryption, bypassing Part 97. Band selection itself becomes part of the compliance architecture.
FT8's price: slowness
FT8 comes from K1JT's (Joe Taylor, discoverer of binary pulsars, 1993 Nobel laureate in physics) WSJT protocol family. It trades an extremely low rate—15-second slots, a dozen-odd bytes per message—for decodability at extremely low signal-to-noise ratios. That's how the 1,600-mile free contact happens. The price of free communication manifests here: not a monthly fee, but bandwidth. In on-device inference we've seen compute substitute for bandwidth (MTP amortizing multiple tokens over one forward pass); FT8 is the mirror operation—time substituting for signal.
This also explains why the creator's bridge does not use FT8 but instead designs custom data frames on the Hermes Lite 2: per the source, "FT8 messages are short, unsuitable for the bandwidth the bridge needs." A weak-signal protocol's capacity can't carry a bridge.
Diffusion notes
The video has million-plus views. The source spectrum is worth noting: Reticulum's early propagation was in prepper and Bitcoin sovereignty-communication circles; in July 2026 Hackaday discussed "post-internet networks," and by September it entered mainstream tech channels. A protocol moved from subculture to a million views with no productizing company in between—just an open-source stack plus community hardware (RAK and Seeed sell Meshtastic kits).
The source mentions that "Reticulum, cheap radios, open-source software, and AI made this individual effort possible"—AI gets one line, no details. Per fidelity discipline, record it without amplifying: going from zero to license plus delivered bridge in three weeks likely involved AI for HF propagation prediction and frame design, but the video doesn't elaborate, so we don't speculate.
Two falsifiable predictions. One: within 12 months, the Reticulum community will ship an "amateur-band compliance profile"—plaintext payloads plus signatures, encryption disabled—semi-formally resolving the Part 97 conflict (discussion #399 is the opening move). Two: as mesh node counts grow, discussion of an FCC review of Part 97's encryption ban will resurface—the word on HN is "the FCC is considering it very slowly," as of 2024—slow enough to double as a forecast.
We end on the deliverables: a 28 MHz dipole, an open-source SDR hand-mounted in its enclosure, a Technician license, and a Reticulum link riding the ionosphere. Wherever cell signal disappears, this link still works—the final segment's blackout test, where a LiFePO4-powered VHF radio kept communicating, is its footnote.
---
*Materials: full video transcript, YouTube original and Data Slayer channel page, Reticulum official ecosystem (nodestar/d-central review, GitHub discussion #399), two Hackaday pieces (HL2 specs 0–38.4 MHz; Reticulum post-internet), FT8 protocol docs (wsjt.sourceforge.io, 15-second slots), Reddit r/ModernRadio results post (09-22), FCC Part 97 §97.113 citations. The 450 nodes and 1,600/727-mile figures are the video's own measurements, not independently reproducible; their magnitudes are consistent with public information.*