HN
Today

MeshCore development team splits over trademark dispute and AI-generated code

A popular mesh networking project, MeshCore, has fractured over a co-founder's secret trademark application and extensive use of "vibe coded" AI-generated software. This dramatic split ignited debates on open-source governance, the trustworthiness of AI in critical infrastructure, and the often-fraught path to commercialization in community-driven projects. The community grapples with two competing visions, forcing a reckoning on what truly constitutes "official" development.

132
Score
80
Comments
#3
Highest Rank
20h
on Front Page
First Seen
Apr 23, 5:00 PM
Last Seen
Apr 24, 12:00 PM
Rank Over Time
1175854345467121111912141616

The Lowdown

The MeshCore project, a rapidly growing mesh networking initiative, has announced a significant split within its core development team. The conflict arose from co-founder Andy Kirby's clandestine application for the MeshCore trademark and his extensive, undisclosed use of "Claude Code"—AI-generated software—across various project components. The remaining core team, staunch proponents of human-written code, expressed profound disappointment and a sense of betrayal.

  • Andy Kirby secretly filed for the MeshCore trademark and built significant parts of the ecosystem using AI-generated code without team knowledge.
  • The original team discovered Andy's actions, leading to a breakdown in communication and an irreparable schism.
  • The "official" MeshCore, according to the original team, is now hosted on meshcore.io, emphasizing its GitHub repository as the "source of truth."
  • Andy Kirby controls the meshcore.co.uk site and the original Discord, using the "MeshCore" brand for his "MeshOS" line.
  • Despite the internal turmoil, MeshCore has experienced rapid growth since January 2025, boasting over 38,000 nodes and 100,000 active users.
  • The remaining "core team"—Scott, Liam, Recrof, FDLamotte, and Oltaco—reaffirms its commitment to high-quality, human-written software.

This unexpected rupture forces the MeshCore community to navigate a fractured ecosystem, choosing between a project emphasizing human craftsmanship and open governance, and another embracing AI-driven development and a contested brand identity.

The Gossip

Code Controversies and AI's Ascent

The use of AI-generated code became a central point of contention. Many commenters debated the inherent quality and trustworthiness of "vibe coded" software, particularly for critical firmware, with some arguing for mandatory disclosure. While some were not inherently against AI use if the code was functional, others highlighted that AI's plausibility doesn't guarantee correctness, making it harder to audit than human-written code.

Trademark Tensions and Project Partitions

The trademark dispute was widely condemned as a "dick move" and a hostile takeover attempt. Commenters discussed the vulnerabilities of open-source projects to commercialization efforts, especially when a single individual attempts to assert brand ownership. Comparisons were drawn to other mesh projects like Meshtastic, sparking a broader discussion on trademark policies in community-driven software and the incentives for "cashing out."

Mesh's Merit and Modern Alternatives

The discussion expanded to the practical utility and limitations of LoRa-based mesh networks like MeshCore. Skeptics questioned the "SHTF" hype, highlighting reliability issues and janky mobile apps. Alternatives like Reticulum and Wifi HaLow (802.11ah) were suggested, though their own challenges were acknowledged. Critiques also surfaced regarding MeshCore's general code quality, lack of automated tests, and even potentially illegal broadcast settings in some regions, suggesting deeper governance issues beyond the split.

Ham Habits and Hacker Hang-ups

A significant tangent explored the culture of amateur radio (HAM) operators, noting a "distinctive personality type" characterized by gatekeeping, a sense of self-importance, and sometimes abrasive behavior. While some commenters acknowledged this stereotype, others highlighted instances of positive community engagement or pointed out that many mesh network users are not HAMs, or are ex-HAMs disillusioned with the subculture's conservatism and internal squabbles.