Why The Split? [Meshcore](blog.meshcore.io)
blog.meshcore.io
Why The Split? [Meshcore]
https://blog.meshcore.io/2026/04/23/the-split
5 comments
tl;dr: a person from the team decided to go all-in on AI slop.
Fortunately, the only resources affected are the .co.uk website and the Youtube channel, the firmware is still in the hands of the core developer team.
Fortunately, the only resources affected are the .co.uk website and the Youtube channel, the firmware is still in the hands of the core developer team.
I was under the impression that meshcore was always vibe coded... people are just noticing this now?
Definitely not, the design was quite carefully made to avoid the pitfalls of Meshtastic. The developers documented quite a lot of their early work. It really didn't feel like a vibe-coded type of environment.
The firmware certainly isn't vibe coded. A heavy amount of the third party tooling however is.
Since being called out on these things, he’s been ghosting the rest of the team. He also happens to control the former official site.