How It Came About
Meshtastic popularized the idea of "chat and telemetry over LoRa." Affordable hardware, mobile apps, a growing community – it attracted many. However, over time the limitations of the architecture became apparent.
Flood routing is convenient but inefficient:
One node shouts "into the forest," all others forward, until the hop limit is reached. For demos, hiking groups, and small networks this is enough. But as a network grows, efficiency collapses:
- too much airtime
- too many duplicates
- too much randomness
This is exactly where Meshtastic remains stuck to this day.
Out of this frustration emerged MeshCore. Instead of packing additional features into an overloaded concept, MeshCore focused on what makes large networks viable in the first place: targeted routing, clear roles, clean configuration – and no functional chaos.
What MeshCore Does Differently Technically
The key difference is simple: MeshCore routes directly.
Not everyone forwards everything, only the next sensible hop does.
This sounds trivial but is the crucial adjustment that decides everything:
- stable airtime
- more predictable latencies
- segmentable networks
- targeted connections instead of randomness
Additionally, there's a clear separation of tasks:
- Repeaters
- Room servers
- Companion devices
Each element has a unique responsibility. Access can be restricted, zones defined, regions coupled via Wi-Fi or Ethernet. The result is no tinkering zoo, but a system with which networks are planned, operated, and scaled long-term.
Why the Dispute Got Heated
Friction was inevitable. Meshtastic developers initially felt sidelined, criticized the lack of attribution in early MeshCore files, and the deliberate incompatibility.
On the other side was the practical question:
Do you want a stable, scalable network – or the next new feature that will be completely rebuilt in a few weeks?
Legally everything is relaxed today:
Open source remains open source. Licenses are correct, origin documented.
Morally, however, there was a scratch. Those who invest years of energy into a project don’t like seeing a fork quickly take over the more professional use cases and many users.
Culture Clashes with Culture
The real difference lies in approach.
Meshtastic:
- centralized leadership
- many ideas
- frequent overhauls
MeshCore:
- decentralized
- pragmatic
- little show
No boss deciding everything, but maintainers who judge based on utility and stability. If an approach proves itself in the field, it is used – not due to a decision but because it works.
Those running infrastructure notice the difference immediately:
less time on version jumps and breaks, more time for planning and operation. Dry, but reliable.
Is "The Scene" Switching?
Technically adept users and some developers are increasingly switching – away from the next feature event, toward reliable stability.
- Meshtastic remains huge and beginner-friendly
- MeshCore grows more slowly, but with clear direction
Additionally, Meshtastic currently faces criticism for moderation practices. Reports are increasing that on the subreddit r/meshtastic, posts and comments containing the word "MeshCore" are automatically filtered or deleted, and users have been banned for it. Similar reports come from Discord.
Such keyword filters feel like censorship, are poorly received, and give the impression that user migration is being prevented.
What Should You Do?
Getting started with both projects is easy:
- Flash the board
- Pair the app
- Go!
Meshtastic fits if you:
- like tinkering
- use MQTT
- want to integrate sensors
- value integrations like Home Assistant
MeshCore fits if you:
- want simple, reliable message transmission
- prefer minimal tinkering
- operate networks longer instead of constantly rebuilding
Turn it on, configure, let it run.
Conclusion
The conflict was inevitable because two goals collide:
- maximum flexibility
- minimal interference
Meshtastic made the idea popular – that deserves recognition.
MeshCore implemented it technically cleanly and sustainably.
Therefore, for larger areas, higher loads, and clear requirements, MeshCore is the better choice.
For small groups and spontaneous use, Meshtastic remains ideal.
For networks you have to take responsibility for, sooner or later there's hardly a way around MeshCore – not out of principle, but due to technical consequence.
It's open source. Both paths may exist.
In the end, you choose the path that gets you to the goal faster.
More and more are doing exactly that – quietly, without drama.
And the radio links stay quiet.