The Internet Is Being Rebuilt Without ISPs

Summary of the video (technological concepts + field test findings)

Goal / experiment

The speaker road-tested how widespread LoRa mesh connectivity is along an East Coast route by using an in-car “portable node” to scan/participate in the mesh while driving roughly 1,500 miles from central Florida to New Hampshire.

Hardware setup (Meshtastic / LoRa)

• Antenna: Installed a 915 MHz magnetic whip antenna via an SMA-mount on the car.
• Power + device: Ran coax into the trunk and connected to a battery-powered R1 Neo device (a consumer-grade node, not a high-power base station).
• Transmit power: Noted the node’s limited transmit power (~22 dBm), designed to conserve battery.
• Network/channel: Used Meshtastic “long fast” public channel presets (explicitly not using a private channel).
• GPS: The device includes GPS and reports location to other nodes.
• Monitoring: Used Bluetooth with Meshtastic on a phone to watch activity and occasionally send messages.
• Potential continuous power: Mentioned the Tesla’s rear outlet could provide USB-C power if needed.

What was observed on the journey

• Node activity varied by location, including an unexpectedly high number of nodes in Concord, NH.
• During an earlier tracking phase on the chosen “long fast” channel, the speaker estimated observing ~15 total nodes, while acknowledging there may be more on other channels/firmware.
• Test messaging worked especially well when crossing bridges:
  • Confirmations often arrived quickly.
  • The speaker described cases where messages were confirmed while passing major bridges, and one instance where a sender reportedly replied while the car was moving through the area.
• Why range improves with elevation / line-of-sight:
  • LoRa benefits from height and line-of-sight.
  • Performance is shaped by interference and Earth curvature.
• Portable node behavior: The portable node acts more like temporary infrastructure than a handheld unit—it can be placed where it has good visibility and operate autonomously.

Why microcontroller-based nodes matter (power + solar)

• Many nodes use MCUs (microcontrollers) rather than full computers.
• MCU efficiency enables autonomous solar-powered nodes.
• The speaker mentioned higher-power LoRa boards (e.g., ~1W capability) as less practical for solar without larger batteries/energy budgets.
• Core takeaway: with lower-power MCUs and roughly ~22 dBm-class operation, solar autonomy becomes feasible.

Reticulum vs Meshtastic (architecture + encryption)

The speaker introduced Reticulum and contrasted it with Meshtastic:

• Meshtastic:
  • With an amateur radio license, users may increase transmission power.
  • The speaker noted this can mean loss of encryption (messages can become unencrypted under certain setups).
• Reticulum:
  • Encryption is effectively mandatory; it’s not easy to “opt out” at the protocol level.
• Micro Reticulum: Mentioned Micro Reticulum, which allows the RNS stack to run standalone on embedded hardware.
• Practical example: The speaker described building a Reticulum transport hub on a Heltec V4, mounted on a drone for aerial infrastructure.
• Repeater-like behavior:
  • Some “nodes in the wild” were in protective enclosures, implying semi-permanent deployments.
  • Reticulum nodes can function similarly to a transport hub (not exactly a traditional repeater, but forwarding/routing in comparable ways).

Scaling behavior: flooding vs routing

• Meshtastic: Uses managed flooding / store-and-forward behavior
  • Broadcast → neighbors rebroadcast → hop limit ends.
• Reticulum: Uses path-based routing
  • Routes are discovered, and transport nodes reuse the path instead of flooding the network.
  • Scaling advantage: improves more with route length than with total network size.
• Reticulum can integrate multiple transport options, such as LoRa, Wi‑Fi, TCP, packet radio, etc.

Real-world resilience test (power outages)

• On arrival in Meredith, NH, a local power grid outage occurred.
• Even after the city lost power, the speaker sent a message over the LoRa network and it was received, framed as a “parallel layer” that can survive grid failures.
• On the return trip, the speaker also experienced another outage event (storm in Charleston).
• Claim: across the trip there were multiple power interruptions (three instances) while the LoRa network remained operational.
• This was used to support the argument for decentralized infrastructure.

Results: larger-than-expected node count

After returning home, the speaker’s node database showed 458 nodes detected total.

The speaker argued that 458 is likely a lower bound because:

• Some nodes use different frequency parameters / encryption keys / firmware stacks.
• Some nodes may simply be out of range when the car passes.

Main implication: there is already community interest and infrastructure, but it’s fragmented.

Interoperability limitations (network fragmentation)

Meshtastic, Mesh Core, and other LoRa networks may not communicate automatically due to mismatches such as:

• Frequency / bandwidth / expansion ratio / encoding rate
• Encryption keys
• Different traffic/routing models

The speaker raised an open question:

• Should Meshtastic infrastructure be merged into Reticulum via software?
• Should boards be reflashed?
• Or should the future be a hybrid of both ecosystems?

Conclusion / thesis: network of networks

The speaker’s thesis is that the “open source internet” isn’t something waiting to be deployed—it already exists locally through these radio networks.

Future vision: a network of networks that combines transport options:

• Internet when available
• LoRa at the periphery
• Wi‑Fi and packet radio where suitable
• Integrated into Reticulum (and potentially other stacks)

---

Main speakers / sources

• Main speaker/source: The video author/speaker conducting the road trip experiment (driving with a Tesla FSD setup, installing a Mouser 915 MHz antenna + “R1 Neo”/Meshtastic node, and discussing Reticulum concepts).
• Referenced creators/projects/vendors:
  • Meshtastic (LoRa mesh ecosystem)
  • Reticulum (RNS stack) and Micro Reticulum
  • Mouser Works / Mouser (for the “R1 Neo” and related hardware)
  • Mesh Core (mentioned as another stack)
  • Heltec (example hardware for Micro Reticulum testing; Heltec V4)
  • FCC / amateur radio license system (speaker’s license approval mentioned)