An Introduction to Meshtastic

Original Article ↗ Hacker News Discussion ↗

Low-power LoRa mesh projects like Meshtastic and Meshcore are drawing interest as off‑grid, decentralized alternatives for text messaging and sensor networks, especially in remote areas, disasters, and hobbyist radio communities. Commenters contrast Meshtastic’s simple, flood-routed, small-group focus with Meshcore’s more scalable routing and fixed-repeaters model, noting that real-world usefulness depends heavily on local adoption and terrain. Alongside enthusiasm for resilience and experimentation, people highlight serious limitations in bandwidth, reliability in dense urban environments, and the social reality that many meshes remain sparsely used despite their technical promise.

Overview & Appeal

  • Meshtastic is a LoRa-based, low-bandwidth, encrypted mesh text system in license‑free bands.
  • Many see it as a fun, HAM‑adjacent hobby with “early internet/BBS” vibes: small, opt‑in communities, low commercialization, technical tinkering.
  • MQTT integration and observability are attractive to some; others like that it works without cell networks or centralized infrastructure.

Meshcore vs Meshtastic

  • Meshtastic: flood‑routed, assumes moving clients; very “chatty” by default. Works well for small groups and ad‑hoc scenarios, but is reported to struggle in dense/urban meshes.
  • Meshcore: separates static repeaters from mobile companions, caches routes, supports more hops. Multiple comments claim it scales better, with a higher share of traffic being actual text instead of telemetry.
  • Regional adoption differs: some areas (e.g., parts of the UK, Pacific Northwest) reportedly favor Meshcore; others report Meshtastic as the dominant, active network.
  • Several note “Meshcore evangelism” in Meshtastic discussions, and push back on “us vs them” framing.

Reticulum & Other Alternatives

  • Reticulum is highlighted as a more general cryptographic networking stack that can run over LoRa, Wi‑Fi, TCP, etc., with proper routing and large hop limits.
  • It’s seen as more ambitious but less user‑friendly; generally not a direct substitute for Meshtastic/Meshcore chat.
  • Other mentions: CellSol, BitChat, and LoRa-based drone control protocols (e.g., ExpressLRS).

Use Cases Discussed

  • Off‑grid and low‑infrastructure comms: hiking, camping, cruises, rural communities, vacation homes with poor cell coverage, boats in the South Pacific.
  • Disaster and SAR: ad‑hoc chains of relays in hurricanes, wildfires, remote logging/fishing camps, ATAK/CivTAK integration.
  • IoT/automation: remote gates, sprinklers, sensors, telemetry, Home Assistant alerts.
  • Prepping, privacy, and experimental networking; some just enjoy “nerdy” chat and range testing.

Limitations, Skepticism & Scaling

  • Many report extremely low real‑world usage: mostly “can you read me” tests, flight nodes, and telemetry; few sustained conversations.
  • Critiques: tiny bandwidth, high latency, fragile flood routing, dense‑area congestion, limited hop count, heavy reliance on well‑placed repeaters, and ease of jamming/locating.
  • Several argue it would “fall over” as a primary emergency system; traditional radios, satellite texting, or internet tunnels may be more practical.
  • Cross‑border censorship resistance is viewed as unrealistic at scale due to power, risk, and bandwidth constraints.

Hardware & Community Notes

  • Cheap boards exist (~$10–30), but many off‑the‑shelf options are reported out of stock; DIY is common.
  • Antenna placement and elevation are repeatedly cited as the main determinants of usable range.
  • There is visible friction around trademarks, branding, cookie banners, and a prior Meshcore split, which some find off‑putting.