[1] https://reticulum.network/ [2] https://lilygo.cc/products/t-echo-lilygo [3] https://github.com/torlando-tech/columba

>And, he’s kept that small detail a secret - that it’s all majority vibe coded.

Without any more context, I am highly suspicious of this framing.

1) Someone "taking over" the ecosystem seems like an entirely different issue. How is this possible? Does it mean he's publishing things and people want to use them?

2) Is the code bad? It sounds like they had no idea he was using AI. That seems to imply there was nothing wrong with the code as-is. Why not judge it on it's merits?

>The team didn’t feel it was our place to protest, until we recently discovered that Andy applied for the MeshCore Trademark (on the 29th March, according to filings) and didn’t tell any of us.

Taking this at face value, this is indeed hostile and bad.

But no, I'm not going to get outraged that someone is simply using Claude Code.

But it sure seems interesting how every time I hear about someone just doing a “rewrite it all with AI“ they seem to turn out to be a giant jerk.

Maybe not the only one. I don’t know enough backstory to judge how trustworthy this post is.

But the signal to noise ratio on my little test above seems pretty good.

[1]: https://meshcore.io

[2]: https://meshcore.co.uk

Highlighting the Claude usage in the headline is a blatant move to bait the anti-AI crowd and farm sympathy points. The real issue has nothing to do with who generated the AST -whether it was meat-ware or a transformer - the issue is the brand hijacking. Stop dragging technology into this; it’s just pure legal scumbaggery

It's ridiculous to me that they're concerned about the trustworthiness of AI-generated code when their code quality is so low. They don't even have automated tests and ignore attempts to add them.[0, 1, 2, 3]

Last I checked, there's little validity checking in the code, so it's possible to broadcast nonsense values (like GPS coordinates outside of Earth's bounds) and the code happily accepts it.

And that's fine if they're just like a scrappy upstart doing their best, but it annoys me to be so high and mighty about their code quality when they don't invest in it.

I really want to like MeshCore but I feel like its stewardship makes it hard. The main two people I know running it are Scott Powell and Liam Cottle, both of whom are trying to build businesses on closed-source layers on top of the firmware. I don't think there's anything wrong with an open-core business model (I ran such a business myself), but it creates perverse incentives where the core maintainers try to suppress information about the open-source alternatives and push their own closed-source paid products.

Also, MeshCore's recommended broadcast settings for the US are illegal.[4] I emailed the Liam and Scott about this months ago, and they ignored me.

[0] https://github.com/meshcore-dev/MeshCore/pull/925

[1] https://github.com/meshcore-dev/MeshCore/issues/1059

[2] https://github.com/meshcore-dev/MeshCore/pull/1065

[3] https://github.com/meshcore-dev/meshcore.js/pull/11

[4] https://github.com/meshcore-dev/MeshCore/issues/945

It is essential to disclose it.

Just a word of caution, claude code might look impressive if your knowledge is shallow or intermediate in a topic, but if you know what you’re doing, once you dig deeper it starts to introduce plenty of scope creeps into your code base, piling one on top of another that you won’t even recognize your own code shortly.

Wifi HaLow 802.11ah is finally out & available, sometimes at ok prices. We don't really have ad-hoc communication pioneered for wifi, but it's doable and we ought lean into it, rather than using some totally different stack, especially one that is under strict control of a single company.

What we learn doing wifi halow can directly port and improve the rest of ways we connect. That would be grand.