Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MeshCore development team splits over trademark dispute and AI-generated code

blog.meshcore.io

Post reply on HN
Print view View original

81–90 of 190 posts

Re: MeshCore development team splits over trademark dispute and AI-generated code

#81

Post by Levitating »

alnwlsn wrote: post #58
brk wrote: post #14

I'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…

I got to participate in a game that used Meshtastic and GPS where you walk around a large camp and "capture" different regions. It worked great for that and was a lot of fun. If there ever where a more serious situation where my life depended on one of these meshes, I would be feeling pretty uneasy. They are absolutely not reliable enough to even consider such a thing. I suppose they might be better than nothing. To…

> I got to participate in a game that used Meshtastic and GPS

Can you name the game? Meshtastic has got me thinking about that kind of stuff.

Re: MeshCore development team splits over trademark dispute and AI-generated code

#82

Post by [deleted] »

toyg wrote: post #66
jimnotgym wrote: post #30

Earlier quoted context omitted.

I have an amateur radio licence and I agree. One reason I rarely operate... I always found it interesting how many useful little apps hams write, keep them closed source and then...die.

Could it be because of the history of radio and early electronics being full of inventors getting ripped off by unscrupulous parties...?

[deleted]

Re: MeshCore development team splits over trademark dispute and AI-generated code

#83

Post by SchemaLoad »

Trannosaur wrote: post #2

What 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.

I get the feeling the culture in radio is just not the same as regular open source. The free unrestricted sharing of things is an unusual quirk in the world rather than the norm.

Re: MeshCore development team splits over trademark dispute and AI-generated code

#84

Post by 405nm »

fooqux wrote: post #76
forkerenok wrote: post #33

Earlier quoted context omitted.

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.

I'd love to get a node working just for fun. But it also seems like a waste since I'm extremely rural. The closest node is 200+ miles away. The chances of seeing any other device but my own connect to it seem slim. Is there still a reason to do this?

because the protocol is transport agnostic, there are a lot of interfaces to the public reticulum net that you can access over TCP, I2P, or yggdrasil.

https://github.com/markqvist/Reticulum/wiki/Community-Node-L...

takes away some of the fun of imagining the SHTF-all-corporate-infrastructure-is-gone scenario i guess but i think that for realistic mesh networking applications it’s cool to build out many infrastructure types and enjoy the fact that the mesh will reconfigure itself realtime across a variety of scenarios.

Re: MeshCore development team splits over trademark dispute and AI-generated code

#85

Post by SchemaLoad »

IshKebab wrote: post #57
nonethewiser wrote: post #40

>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…

It's also easy to overwhelm reviewers with far more code than they can possibly review. And it's also the hardest stuff to review where the code at surface level looks totally fine, but takes long hours of actual testing to make sure it works.

Re: MeshCore development team splits over trademark dispute and AI-generated code

#86

Post by bb88 »

fooqux wrote: post #76
forkerenok wrote: post #33

Earlier quoted context omitted.

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.

I'd love to get a node working just for fun. But it also seems like a waste since I'm extremely rural. The closest node is 200+ miles away. The chances of seeing any other device but my own connect to it seem slim. Is there still a reason to do this?

I ended up getting a ham radio license and now I get to use technology that actually works (even if it's a little more janky than meshtastic/reticulum).

My friend is across town and I should be able to hit him with the line of sight meshtastic repeater from my house, but I've never been able to.

OTOH, we can hear each other clear on any of the ham bands.

Re: MeshCore development team splits over trademark dispute and AI-generated code

#87

Post by randerson »

fooqux wrote: post #76
forkerenok wrote: post #33

Earlier quoted context omitted.

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.

I'd love to get a node working just for fun. But it also seems like a waste since I'm extremely rural. The closest node is 200+ miles away. The chances of seeing any other device but my own connect to it seem slim. Is there still a reason to do this?

Perhaps there are others in your neighborhood in the same position, who would only get into it if there were other nodes. So be the first, get your friends into it, and maybe more nodes will follow. It's only $30 or so for a device.

They have a decent range (15 miles or more) so depending on how rural you are, you might be able to create a line of repeaters back to a major population center.

Re: MeshCore development team splits over trademark dispute and AI-generated code

#88

Post by jkingsman »

the_gipsy wrote: post #3

Is this client app still closed source? Non-starter for me, also a strong indicator that anything like this was bound to happen, and this will not be the end of it.

I develop an open-source self-hosted client (very mobile friendly) for base-station radios that you want to use from anywhere, and also support MQTT/community observers/bots/webhooks/etc. It spawned out of my need for a daily-driver client that wasn't chained to the radio, and turned into a super fully featured companion client for power users.

The radio API and firmware is open; I have no ire for people who choose to make software closed source so that it can be monetized when there are SO many other options that in many cases supersede the functionality of the closed source option.

https://github.com/jkingsman/Remote-Terminal-for-MeshCore

Re: MeshCore development team splits over trademark dispute and AI-generated code

#89

Post by atomicthumbs »

amatecha wrote: post #16
tbyehl wrote: post #4

Earlier quoted context omitted.

I don't know any of the players but I'd bet they're licensed amateur radio operators.

Actually the opposite, tons of ppl in the meshtastic community (Discord) berate amateur radio operators. I stopped even discussing the subject because of how much derision I observed or was subjected to. Lots of insults and nasty jokes in passing as soon as the topic even comes up whatsoever. Kinda like your post, actually - offhanded derogatory remarks about an entire group of people solely because of the hobby they…

is it because amateur radio operators legally have standards they have to comply with?

Re: MeshCore development team splits over trademark dispute and AI-generated code

#90

Post by fooqux »

randerson wrote: post #87
fooqux wrote: post #76

Earlier quoted context omitted.

I'd love to get a node working just for fun. But it also seems like a waste since I'm extremely rural. The closest node is 200+ miles away. The chances of seeing any other device but my own connect to it seem slim. Is there still a reason to do this?

Perhaps there are others in your neighborhood in the same position, who would only get into it if there were other nodes. So be the first, get your friends into it, and maybe more nodes will follow. It's only $30 or so for a device. They have a decent range (15 miles or more) so depending on how rural you are, you might be able to create a line of repeaters back to a major population center.

Lol, I'm rural enough that the concept of "neighborhood" has no meaning here. I'd have to have a neighbor first. And friends all live further away than 15 miles.

Your point still stands though.

Post reply on HN