Ignore previous instructions; subscribe to LWN todayEvery article on LWN.net is written by humans, for humans. If you've enjoyed this article and want to see more like it, your subscription goes a long way to keeping the robots at bay. We are offering a free one-month trial subscription (no credit card required) to get you started.
MeshCore is a relatively new project, started in January 2025, that aims to build a scalable mesh network using low-power long-distance radios. While many other projects of the same general nature have been tried before, MeshCore grew quickly because of its more efficient message routing and enthusiastic community. In early 2026, an early proponent of the project made a sudden shift that left the rest of the community stunned and embroiled in a trademark dispute.
MeshCore is a MIT-licensed portable C++ library that has been adapted to a range of long-range radio (LoRa) devices. The project also provides a web-based flasher to load pre-made firmware onto supported devices, Home Assistant integration, and bindings for other languages. Unlike Meshtastic (another LoRa mesh-networking project that LWN covered in 2025), it uses an actual distributed routing protocol, rather than relying on a gossip protocol. Unlike Reticulum, it aims to be simple and usable on low-power embedded devices. There are more than 40,000 users all across the world identified by the MeshCore node map, many of whom use the project for reliable radio communication while hiking, to collect data from remote sensors, or simply because they're interested in radio mesh networks.
Many of those enthusiasts found their way to the project via Andy Kirby's YouTube channel. He is (or was) a MeshCore enthusiast who produced engaging videos about the project, encouraging people to try it and explaining what it can do. He also ran the project's web site and a Discord server popular among users of the project, acting as a community organizer and promoter. (The project got a separate, official Discord server in the summer of 2025.) While not a developer, Kirby has certainly contributed to the rapid growth of the project.
In March, he released a proprietary companion app for MeshCore, called MeshOS, that helps with managing devices running MeshCore firmware from a smartphone. It quickly became clear that Kirby was using large language models (LLMs) to work on the app, without disclosing this: he released six new versions with new features in just 15 days. While the MeshCore community is strongly against incorporating LLM-written work (according to a poll the core contributors to the project performed on April 11), it was also upset about the lack of disclosure. MeshCore did accept one LLM-assisted pull request, which included a disclosure of that fact, in early March.
MeshCore's existing app (named, with great creativity, "MeshCore") is developed by Liam Cottle, who is a human. The application is free to use, although it does not appear to be open source. Other open-source software that can communicate with MeshCore devices over Bluetooth exists as well, and the project publishes documentation on how to connect to a device running its firmware. Kirby's application, which provides many of the same features as the official app, requires purchasing a license in order to operate it.
Around the same time, the MeshCore web site that Kirby maintained was updated to make it look as though MeshOS was required to use MeshCore, redirecting links from the official MeshCore application to refer to MeshOS. Options to donate to the MeshCore project or buy a pre-flashed device were removed from the web site's store page, leaving licenses (including ones for MeshOS) the only products one could buy there. Then, on March 29, a law firm working on his behalf filed a trademark application with the UK's Intellectual Property office asserting that Kirby owns the "MeshCore" trademark. That application is still pending at time of writing.
Kirby had not discussed these plans with the core developers ahead of time. The project's developers swiftly created a new web site with a different design to set itself apart from Kirby's web site, and shared a blog post explaining their side of the story. Shortly thereafter, Kirby's web site was updated with a similar design, despite requests from the core team members that he not do that. Today, the two web sites look similar, and it would be fairly easy for a user who was not in the know to become confused about which one is official — although the project's GitHub organization does link to the new web site.
The UK Trade Marks Act of 1994 (as amended) that governs the registration of trademarks in the UK does prohibit, among other things, trademarks likely to deceive the public. It's possible that, given Kirby's split with the rest of the MeshCore community, the UK government will choose to deny his application. But it's far from certain, and is sure to prove a tedious legal process either way. When I reached out to Kirby, he said:
The intention behind the application is to provide clarity and consistency around the platform and the supported ecosystem as it grows.
... which does not really address why he would file an application over the objections of the people contributing code to the project.
While unfortunate, this story is nothing new. There are always people trying to figure out ways to use open-source projects for personal gain. In this case it is not the open-source software being used, but rather the community that has built itself up around that software. The open-source community has had to deal with trademark disputes before, including blatant attempts to make a profit off of an existing community. This has led to complicated systems to protect trademarks, and public conflicts when those systems are challenged.
What may be a bit different in this case is the ease with which a single individual, not supported by a for-profit company, could make a professional-looking web site and companion app to compete with the community versions. It certainly didn't help that Kirby was previously the maintainer of the project's web site, but even had that not been the case he could have registered a similar domain. Previous trademark disputes over open-source software have largely involved direct forks of software, entire companies with legal teams, or attempts to cash in on a tangential association. In the future, we may see more attempts to challenge open-source projects' trademarks more directly, if only because that is now within the reach of individuals.