The key takeaway from this is that drama loving dinosaurs live among us. Moving on.
I'm ignoring the attempted trademark trickery because TLDR; blah AI is evil blah blah other stuff.
MeshCore development team splits over trademark dispute and AI-generated code
101–110 of 190 posts
Re: MeshCore development team splits over trademark dispute and AI-generated code
#102I've played with MeshCore and Meshtastic a bit, and while they are fun, the general hype seems overblown. The "SHTF" types that get involved with this tend to just taint the whole concept for me. I was/am interested in the use cases for building sensor networks, but most of the chatter seems to be around people who just want to send Hello World type texts back and forth, without realizing how poorly a network like th…
SHTF?
Often refers to doomsday preppers.
Re: MeshCore development team splits over trademark dispute and AI-generated code
#103Earlier quoted context omitted.
I've never seen a working Reticulum network in the wild. Only very very small testbeds.
There are tons of entry points available now [0], and I get thousands of announcements every day. https://rmap.world/ 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.
> There are tons
I'm sorry but are you serious? That map shows 224 nodes in the world, fewer than 30 in the entire Western hemisphere. And only 24 in the world are using LoRa? Meshcore has 38,000 nodes, Meshtastic 10,000. Those two projects can actually be said to have "tons" of nodes.
It hurts your credibility. I trusted you, spent time trying to debug the map, thinking that something was wrong on my end... why am I only seeing 224 when there should be "tons", is there a filter, are these just super nodes....
So I looked into it because of what you said, but you raised expectations so much that I feel nothing but disappointment.
Re: MeshCore development team splits over trademark dispute and AI-generated code
#104What is it with mesh projects and having these super draconian trademark enforcers? Meshtastic is the same. One of the main reasons I got interested in MeshCore was reading the Meshtastic trademark rules and just finding them... really really over the top.
The protocol is CC and Mark has said go wild, it seems he doesn't want his work to contribute to an unstoppable AI killing machine networm
Re: MeshCore development team splits over trademark dispute and AI-generated code
#105>We have always been wary of AI generated code, but felt everyone is free to do what they want and experiment, etc. But, one of our own, Andy Kirby, decided to branch out and extensively use Claude Code, and has decided to aggressively take over all of the components of the MeshCore ecosystem: standalone devices, mobile app, web flasher and web config tools. >And, he’s kept that small detail a secret - that it’s all…
> 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? Anyone that has used AI at all knows this isn't how it works. AI is extremely good at producing plausible-but-wrong outputs. It's literally optimised for plausibility, which happens to coincide with correctness a lot of the time. When it doesn't you get…
Do folks not write tests and review their own code (AI generated or not)?
Also, citation needed:
> With human written code it's a lot easier to tell if it's good or not
Re: MeshCore development team splits over trademark dispute and AI-generated code
#106Earlier quoted context omitted.
> 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. Yes, old mildly misogynist, mildly racist, wellakshually, holier than thou, pro-trumper types. I was there at Dayton Hamvention (2024) when they had to turn off the 2M repeater because 2 or 3 of them got into a screaming match over trump. Na…
It's not even just a pro-trump thing. That's not even the thing particularly annoying about hams because that's annoying across all of society. I can tolerate disagreeing with peoples opinions but not disagreeable/disharmonioous behavior. Hams act super gatekeepey and act insanely protective/defensive around things that don't actually belong to them. They tend to have a high sense of self-importance around their skil…
[deleted]
Re: MeshCore development team splits over trademark dispute and AI-generated code
#107Earlier quoted context omitted.
> 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? Anyone that has used AI at all knows this isn't how it works. AI is extremely good at producing plausible-but-wrong outputs. It's literally optimised for plausibility, which happens to coincide with correctness a lot of the time. When it doesn't you get…
Just read the code. There is nothing keeping people from reading the code.
I can't find the source code either for the official MeshCore app or for MeshOS -- where can I read the code?
Re: MeshCore development team splits over trademark dispute and AI-generated code
#108Earlier quoted context omitted.
Just read the code. There is nothing keeping people from reading the code.
I can't find the source code either for the official MeshCore app or for MeshOS -- where can I read the code?
It's so weird right? I keep hearing people say it's open source but like... where's the code then? I've tried to find it. I can find stuff for core components, but they lock features behind a delay-wall in the app. If it was open source that stuff would be gone immediately.
Re: MeshCore development team splits over trademark dispute and AI-generated code
#109Re: MeshCore development team splits over trademark dispute and AI-generated code
#110Aggressive promotion by badmouthing any other mesh, and now this - seems rather British. :)