I would absolutely encourage everyone reading this to check out Reticulum [1] if you haven't already. I believe the base project might be in need of new maintainers(?) at the moment and the main dev has some very strong takes, but it is a very well-thought out approach to distributed networking at the protocol layer. The existing implementations out there include a desktop app which can function over the internet (IP…
MeshCore development team splits over trademark dispute and AI-generated code
31–40 of 190 posts
Re: MeshCore development team splits over trademark dispute and AI-generated code
#32Wifi 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.
Re: MeshCore development team splits over trademark dispute and AI-generated code
#33I would absolutely encourage everyone reading this to check out Reticulum [1] if you haven't already. I believe the base project might be in need of new maintainers(?) at the moment and the main dev has some very strong takes, but it is a very well-thought out approach to distributed networking at the protocol layer. The existing implementations out there include a desktop app which can function over the internet (IP…
I've never seen a working Reticulum network in the wild. Only very very small testbeds.
It's so much fun with little pages, message boards and random people hitting you up for a chat. I brought up my own transport node and propagation node too to contribute to the mesh.
Re: MeshCore development team splits over trademark dispute and AI-generated code
#34I would absolutely encourage everyone reading this to check out Reticulum [1] if you haven't already. I believe the base project might be in need of new maintainers(?) at the moment and the main dev has some very strong takes, but it is a very well-thought out approach to distributed networking at the protocol layer. The existing implementations out there include a desktop app which can function over the internet (IP…
I wish nomadnet got rewritten in Go.
Re: MeshCore development team splits over trademark dispute and AI-generated code
#35I would absolutely encourage everyone reading this to check out Reticulum [1] if you haven't already. I believe the base project might be in need of new maintainers(?) at the moment and the main dev has some very strong takes, but it is a very well-thought out approach to distributed networking at the protocol layer. The existing implementations out there include a desktop app which can function over the internet (IP…
I wish nomadnet got rewritten in Go.
at the very least, try it. maybe it's simpler than you think
Re: MeshCore development team splits over trademark dispute and AI-generated code
#36Re: MeshCore development team splits over trademark dispute and AI-generated code
#37> Would you trust AI generated mesh firmware ? 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…
Re: MeshCore development team splits over trademark dispute and AI-generated code
#38Earlier quoted context omitted.
So?
IYKYK. Hams are known for a distinctive personality type that can be at strong odds from other tech people and other comms people. Usually in ways that clash with consequences. I know a few hams that are chill and they are precious doves. I know quite a few more who I won't even engage with for fear of crossing them and them dedicating their lives to making mine hell. Because I've seen them do it to others. That's no…
Re: MeshCore development team splits over trademark dispute and AI-generated code
#39Re: MeshCore development team splits over trademark dispute and AI-generated code
#40>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.