Live data from Hacker News

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

blog.meshcore.io

11–20 of 190 posts

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

#11

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.

Wow, very surprised to learn that it is closed source, and that's probably not changing. My local mesh was testing out meshcore last week, this definitely kills my interest too

Thankfully there is an open-source client, which has pretty much all the features of the main client as well as some extras.

https://github.com/zjs81/meshcore-open

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

#12

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.

Wow, very surprised to learn that it is closed source, and that's probably not changing. My local mesh was testing out meshcore last week, this definitely kills my interest too

This reduced my interest to zero in this as well, when I learned it was closed source

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

#13
post #10

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

What is IYKYK ? If you know you know?

yeah

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

#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 this would perform in a real SHTF scenario.

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

#15
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) or a USB connection to some existing LoRA boards. I recently purchased a LilyGo T-Echo [2] and have had a great experience flashing the open-source firmware and using it connected to a desktop over USB or connected over Bluetooth to the fantastic new companion app Columba [3]. This app seriously makes Reticulum feel like a first class citizen when it comes to parity support for messaging. You can even send files/images (with limitations of course)! And since it works at the network level, you can make your own apps to run over Reticulum as well.

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

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

#16
post #4

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 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're involved in.

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

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

SHTF?

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

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

SHTF?

Shit Hits The Fan.

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

#19

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.

Wow, very surprised to learn that it is closed source, and that's probably not changing. My local mesh was testing out meshcore last week, this definitely kills my interest too

Shame to hear that: the protocol works well, scaling up to thousands of nodes across hundreds of miles. This is the local mesh where I live: https://cascadiamesh.org/map/

You don't have to use the closed source app; there's an open-source client too, there are Blackberry-style client devices which don't require an app at all, and all the actual firmware is open source (MIT).

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

#20

Earlier quoted context omitted.

Wow, very surprised to learn that it is closed source, and that's probably not changing. My local mesh was testing out meshcore last week, this definitely kills my interest too

Shame to hear that: the protocol works well, scaling up to thousands of nodes across hundreds of miles. This is the local mesh where I live: https://cascadiamesh.org/map/ You don't have to use the closed source app; there's an open-source client too, there are Blackberry-style client devices which don't require an app at all, and all the actual firmware is open source (MIT).

Wow, the coverage is nuts. I should hop on, looks like I've got solid coverage in my area. Been too lazy to properly give it a try but obviously I really should! Thanks for the link!
Post reply on HN