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

https://blog.meshcore.io/2026/04/23/the-split

by wielebny • 3 months ago

285 182 3 months ago

blog.meshcore.io

Trannosaur• 3 months ago

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.

tbyehl• 3 months ago

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

fooqux4• 3 months ago

So?

amatecha6• 3 months ago

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.

linsomniac2• 3 months ago

I will say in Northern Colorado a LOT of the people involved in the MeshCore are HAMs.

walrus015• 3 months ago

Speaking as a person who works professionally in fcc part 101 licensed point to point microwave systems carrying IP data, I have less than zero patience for the BS and shenanigans of analog ham radio enthusiasts.

They always want to posture as if they'll be some critical service every emergency responder comes running to in a major disaster and it rarely if ever happens.

In the interests of not reinventing the wheel, you can see here in the same thread the comment from many other posters about the problems that they have with the behavior, attitude, and perspective of many ham radio operators.

queenkjuul2• 3 months ago

All meshtastic code is GPL, the name "meshtastic" is owned by the company that developed it. You can use any of the code, you can't use their name outside their rules. This is absolutely no different than, say, Firefox. The trademark policy is very permissable and you don't even need their permission to use the name on a commercial product.

I think it's totally sensible for the organization to want to have some level of control over what gets their label on it -- the Wi-Fi people wouldn't be very happy about someone slapping their logo all over a bunch of completely incompatible hardware.

toyg2• 3 months ago

Nitpicking, but IIRC, Wi-Fi was born largely as a marketing effort rather than a technical one. Interoperability was an afterthought.

celsoazevedo4• 3 months ago

For now, I don't think it's fair to compare MeshCore with MeshTastic in terms of enforcement as that has not happened with MeshCore. This seems to be one guy getting a trademark in the UK without the approval of other members of the team. They're not going after anyone. Not yet, at least.

mschuster912• 3 months ago

What is it with mesh projects and having these super draconian trademark enforcers?

Simple. Follow the money. Meshcore has more than 100k of users, repeaters are cropping up like weeds across the world. And that means there is a serious incentive to "cash out".

Notably, the person "cashing out" here wasn't involved in Meshcore firmware or app development, but in marketing.

SchemaLoad2• 3 months ago

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.

cge• 3 months ago

In my experience, amateur radio (both licensed and license-free) and 3d printing both seem to have cultural perspectives on open source that differ considerably from the regular open source software community.

But while in 3d printing, outside of hardware, that difference often feels confused (eg, I've seen the Multiboard creator post compliments online about models that blatantly violate his own license), in radio the difference often feels hostile. You have OpenGD77, for example, with its 'we were never GPL' rug-pull that was likely illegal (they had outside contributions) [1]. You have Meshcore with its 'we are open source, except...', and, as you can see in this thread, a difficulty actually finding parts of the code. You have the heavy cultural push against uSDX (seemingly open hardware+source) toward truSDX (DRM-encumbered), and what seems like the quiet acceptance of things like QMX, where you can solder together a radio with DRM that prevents you from installing your own firmware. You even have digital modes that are legally required to be publicly documented, and actually aren't in any meaningful way: VARA FM is probably the worst offender [2], but even modes that are in-crowd enough to be advertised in FCC license exam questions are often effectively proprietary and legally dubious.

What's particularly foreign to me about the culture is that oftentimes, much of the community seems to support behavior that seems malicious from an open source perspective, and attack the open source proponents.

[1] https://hackmd.io/@ajorg/opengd77-is-closed [2]: https://themodernham.com/reverse-engineering-vara-fm-part-1-...

pwndByDeath• 3 months ago

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

zobzu• 3 months ago

they all hope to make lot of money of of it. meshcore has a marketing team spamming reddit all day and a mao to make you believe people use it right now. then you connect to yhe mesh and you're utterly alone there. at least meshtastic has real users lol.

the_gipsy• 3 months ago

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.

queenkjuul2• 3 months ago

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

drpfenderson• 3 months ago

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

sidewndr46• 3 months ago

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

marssaxman2• 3 months ago

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

LaserBeam10002• 3 months ago

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

The closed client isn't needed anymore.

jkingsman• 3 months ago

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

desireco42• 3 months ago

I love using AI to develop and I think it is important in modern development, but you definitely have to disclose it because there is a difference between AI and human written code is key.

It is essential to disclose it.

CyberDildonics2• 3 months ago

You're right, I don't know who would down vote or disagree with this. It's not easy to figure out what a program is doing, but if someone wrote it you at least know there was some sort of intention there. With AI you have no idea why it's there.

All over the internet people are putting up vibe coded projects and no one says that's what it is up front. They all just say "I made this" and they are more than happy to take in the adulation of people impressed that they made something with an animated pattern.

Then when they finally admit that they wrote nothing and don't know how any of it works people start to say "nothing wrong with using ai", as if using it is the same as copying it verbatim, not understanding anything and taking complete credit as if you wrote it while lying about how it was used.

preisschild• 3 months ago

Not only because of that, but if you vibe code huge parts of the project, it is questionable if you really have the rights to agree to the Developer Certificate of Origin and to license it under that specific code bases LICENSE.

brk2• 3 months ago

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.

Insanity• 3 months ago

SHTF?

brk2• 3 months ago

Shit Hits The Fan.

EdwardDiego• 3 months ago

Often refers to doomsday preppers.

RankingMember• 3 months ago

I feel the same way, and both mobile apps are pretty janky, with Meshtastic being extra obnoxious because the UI teams between Android and Apple apparently don't talk to each other- very hard to onboard/answer questions from someone new if you're on a different platform than them.

It was fun and cheap to set up, but I look forward to something with better messaging persistence so you can at least reliably not miss stuff.

alnwlsn2• 3 months ago

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 say nothing of what is required to set up the devices. I wanted to put a full dev system on a raspberry pi 3 just so it would all be in one place and I could work on it when in a location with no internet - it ran out of memory trying to compile the massive web app that is the default client interface.

Levitating2• 3 months ago

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.

takipsizad• 3 months ago

I largely agree and want to add more,I also think the lack of standards also will effect it's usability in a real shtf scenario. why should I use meshstastic over meshcore for example. I also don't think lora will be in my mind in that kind of scenario.

MiracleRabbit2• 3 months ago

If you want to build sensor stuff you should have a look a LoRaWAN.

Get a basestation from Mikrotik and use Chirpstack as backend.

This setup is commercially very very battlefield proven.

komali25• 3 months ago

SHTF

We have a pretty big meshtastic/meshcore / reticulum scene in Taiwan organized through g0v's civic defense group. It's a nontrivial issue for us when the PRC keeps cutting our cables - which is why Audrey Tang was hitting up Starlink back when they were the digital minister.

Basically we very much may need these secondary networks someday.

I really want to get plausible "Walkaway" intranet set up here with e.g. mirrored Wikipedia and whatnot, I don't know enough yet to do that though.

https://zh.wikipedia.org/zh-tw/G0v%E9%9B%B6%E6%99%82%E6%94%B...

lukeasch21• 3 months ago

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

LaserBeam10002• 3 months ago

I've never seen a working Reticulum network in the wild.

Only very very small testbeds.

forkerenok3• 3 months ago

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.

anthk2• 3 months ago

I wish nomadnet got rewritten in Go.

forkerenok3• 3 months ago

There's a maturing implementation of the whole stack in go, so this is not far off.

NooneAtAll32• 3 months ago

be the change you want to see in the world :)

at the very least, try it. maybe it's simpler than you think

adammarples2• 3 months ago

Which frequency do you get? Does it matter?

jonah• 3 months ago

It matters legally.

Different countries allow unlicensed use on different frequencies. Look up which is correct for your location.

montyanne• 3 months ago

I spent an entire month trying to build something with Reticulum, but there just isn’t great tooling for dealing with the protocol. Makes for a pretty infuriating devex if you’re just trying to build your app.

Neat concept but so many footguns that (imo) it’s not really sustainable to try bootstrapping.

Specifically, I had tried to port the stack to Rust no-std to use on nrf52 LoRA devices to use/abuse the existing MeshCore network to deliver reticulum packets. Turned out to be a nightmare just trying to figure out if my packets were even correctly formed.

fragmede3• 3 months ago

Why is Reticulum and MeshCore the issue here and not rust?

405nm3• 3 months ago

don’t forget that although it already works fine on lora, it’s a protocol that’s transport channel agnostic, and is gonna do great with other transports (halow, optical, wifi, whatever) when people finally start realizing that lora is never going to be able to keep up with bandwidth/speed requirements of anything much beyond simple text messaging.

although, i’ve already done real time voice calls over 1 hop of reticulum lora on and it works pretty ok.

edit - community wiki with getting started instructions is here:

https://reticulum.miraheze.org/wiki/Welcome

Levitating2• 3 months ago

simple text messaging

Also great for position tracking, sensor data or motion detection etc.

mtlynch5• 3 months ago

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

jstanley2• 3 months ago

What's an example of a GPS coordinate "outside earth's bounds"?

mtlynch5• 3 months ago

A longitude that's outside the range of [-180, +180] or a latitude that's outside the range of [-90, +90].

ted_dunning2• 3 months ago

32˚N 80˚W altitude 1000 miles

NooneAtAll32• 3 months ago

what's even the need to transmit/receive GPS as part of the protocol?

randerson2• 3 months ago

Its optional but it helps to see where nodes are on a map, and would be useful in (for example) a search & rescue operation.

nonethewiser5• 3 months ago

Would you trust AI generated mesh firmware?

This is also a loaded question. The only specifics they've offered are that he simply used Claude Code. Um... OK? Do the tests pass? Did his changes add any security flaws? Regressions that were untested?

mschuster912• 3 months ago

It's ridiculous to me that they're concerned about the trustworthiness of AI-generated code when their code quality is so low.

Agreed, but at least it's somewhat sensibly structured. AI? Good lord you'll end up with a slopaghetti mess.

They don't even have automated tests and ignore attempts to add them.[0, 1, 2, 3]

Two people, 540 issues and 270 PRs open at the moment. Not wanting to be that guy... but do the math. The reviewer team is small as hell and after this drama (which probably kept both of them busy with BS) they'll likely be even less willing to trust others.

If you want to stand a better chance at getting your code into other people's hands, go and contact the person behind the Evo fork. IIRC he's part of Hansemesh, Germany's biggest regional MC.

I have heard indirectly multiple times now that the only two ways to get a PR of interest merged is to either gather enough people to Like the issue on Github or to join the Discord and ask.

[1] https://github.com/mattzzw/MeshCore-Evo

kstrauser• 3 months ago

Wow, #4 is frustrating. (Disclosure: am a ham, but not one of the uptight ones. I'm not personally offended when someone breaks the rules, and I'm not gonna run off and call the FCC or something. But I am concerned when they don't seem to know or care why.)

First, I don't know if their interpretation of the rules is correct. For the sake of argument, I'll assume it is. More importantly, most other people in that thread seem to be going along with the idea that it is correct. This is how it reads to me:

Submitter: We're violating the rules and should make this change.

Replier 1: That change would be inconvenient in Seattle so we're not doing it.

Replier 2: It wouldn't work well in Boston, either, so it's a no-go.

Part of me wants to shake them. This isn't 'Nam. There are rules. Whatever you think about the FCC regulations, they're not voluntary, and they certainly don't have an opt-out for "it wouldn't work as well that way". To a first approximation, everyone else using the public airwaves is more or less following the law. If following the law makes your project not work as well, that's your problem. It's on you to fix your project so that it's legal to use.

I'm not one of those old hams who gets hyper cranky about this stuff, but I do understand how they come to be that way. The only reason we can use the spectrum at all is that people are mostly using it legally so that their work isn't interfering with everyone else trying to use the same public resource.

thih9• 3 months ago

As they say, there is an .io[1] website with the "MESHCORE" logo, and a .co.uk[2] website with the "MESHCORE(tm)" logo.

[1] https://meshcore.io

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

jauntywundrkind2• 3 months ago

Spicy take but I think this whole Lora thing is a dead end bad technology not worth our time.

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.

HNisCIS• 3 months ago

Eh, I've played with 802.11ah and it's very long range for the power, but way too stateful for the use case that these mesh protocols serve. If you go out of range it's several seconds to re-establish a connection. I've worked with proper mesh radios (Silvus, etc) and they work very differently.

Avamander• 3 months ago

The 802.11ah offerings right now are a mess though. Mostly proprietary and just generally very buggy. I don't know of a single chip that can actually be used with up-to-date Linux. Do you? Be it Morse Micro, Newracom, Taixin or any other, they all suck in some aspect.

Hostapd people also do not seem interested in bringing in any 802.11ah support. So it's crap in that aspect as well. Drivers all fake 802.11n or the chipset offers some garbage AT-command interface and does all of the networking.

On the other hand MeshCore and Meshtastic have similarly terrible codebases as far as I've seen. At least they're somewhat usable though.

Honestly no clue why these software stacks are all this dangerously written, unstable and haven't improved in years.

KurSix3• 3 months ago

Mesh networking is still mostly a playground for hobbyists and hacky, built-on-the-knee implementations. People love shipping a cool PoC, but as soon as the boring stuff starts - stabilization, drivers, edge cases - everyone bails to chase the next hype protocol. We’re left with mountains of half-baked C++ legacy that nobody dares to refactor because the whole house of cards would collapse iirc

walrus015• 3 months ago

LoRA is extensively used in Ukraine right now as a UAV control rf link to bridge serial uart from ground control system to uav. In its most narrow channel configurations at lower bps and using things like 1.2GHz tuned yage antennas it can have some very robust jamming resistance.

MiracleRabbit2• 3 months ago

Wifi HaLow 802.11ah

LoRa is another level. It works down to -146dBm.

802.11ah dies around -100dBm.

Still much much better than "standard" Wifi. But you are comparing two different beasts.

nonethewiser5• 3 months ago

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

prism56• 3 months ago

Agreed. I use meshcore and have multiple repeaters setup. I don't care about people using ai assisted coding but I think it should be disclosed especially if its closed source.

Now the trademark take over seems crazy especially given Andy hasn't contributed to the github project, only personal for profit add ons.

I do also think that the meshcore core team have "tacked on" and tried to enforce a stronger narrative with their anti ai coding bias.

consp• 3 months ago

only personal for profit add ons

In that context it is quite logical to take a trademark out once the project is mature enough so you can profit off other people's work.

Considering their user base does not like the hidden vibe coded idea I don't think this is bias but a sane rationalisation.

jeromegv2• 3 months ago

It wasn't ai assisted coding, it was vibe coding from someone with no real coding background. A communication protocol can't be vibe coded, how do you enforce security if the person is unable to understand what the tool created?

Especially when they try to hide that they were using those tools in the first place

IshKebab• 3 months ago

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 code that seems good and is therefore very difficult to judge on its merits.

With human written code it's a lot easier to tell if it's good or not.

There are exceptions to this - usually if you have some kind of oracle like that security work that used AddressSanitizer to verify security bugs, or if you're cloning a project you can easily compare the behaviour to the original project. Most of the time you don't have that luxury though.

SchemaLoad2• 3 months ago

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.

doug_durham• 3 months ago

Just read the code. There is nothing keeping people from reading the code.

securicat• 3 months ago

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

nonethewiser5• 3 months ago

If the code is bad why not lambast him for pushing bad code? If he's pushing straight to main why have such shitty controls? If it got through review whats the problem? AI in-and-of-itself is not bad. They never substantiate beyond saying he used Claude Code a lot.

axegon_2• 3 months ago

Disagree: I applaud them for doing this. Anyone that says they've reviewed the 1000 lines of slop any AI has spit out is simply lying to everyone and even potentially themselves and has never done a single extensive code review in their life. Reading 1000 lines of text is one thing, reading and analyzing the complexity implications and edge cases in code - no chance. The "I've reviewed the slop" response is the reasons why 0 days and leaks are happening more than ever: because no one really reads the code cause "I vibe-coded it". An extensive and comprehensive code review may take days, and no slopper has ever done that. I'll get a 100 line pr and going over it can easily take hours, especially when something looks wrong and I need to test it. And it's a good reason why I'd never trust the "You are absolutely correct, apologies for the oversight, here's a revised version:"

nonethewiser5• 3 months ago

Disagree: I applaud them for doing this. Anyone that says they've reviewed the 1000 lines of slop any AI has spit out

You're assuming the thing in question - that it's just AI slop. They dont offer any insight on that - they merely say he used Claude Code a lot. It shows a real lack of understanding of AI tools to equivocate those two things.

tamimio• 3 months ago

Ah, the cliche story of most open source projects! Still, that was a dick move to hijack the project just because you were the “front end” or the promoter, and found that AI can help so you backstabbed the team and hijacked the trademark as well, class A a-hole!

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.

KurSix3• 3 months ago

It’s hilarious how people are blaming Claude for a human being a total snake. Trademark squatting is the oldest legal trick in the book. AI just gave Andy the leverage to fake "official" status and look busy while the rest of the team did the actual heavy lifting. The tech just fast-tracked the inevitable fallout tbh

MBCook• 3 months ago

I’ve never used this project and don’t know anyone involved.

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.

webprofusion2• 3 months ago

The key takeaway from this is that drama loving dinosaurs live among us. Moving on.

webprofusion2• 3 months ago

I'm ignoring the attempted trademark trickery because TLDR; blah AI is evil blah blah other stuff.

jolly-good• 3 months ago

Aggressive promotion by badmouthing any other mesh, and now this - seems rather British. :)

KurSix3• 3 months ago

It’s funny how a standard power grab over cash and control is being packaged as some "Holy War against AI"

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

mg794613• 3 months ago

Lovely, another open source rugpull.

Is this the new way? Attract a lot of developers, and when you think you can sell the product , you take all their code and call it your own.

Has this worked out for someone so far?

sealWithIt• 3 months ago

I think it was a good decision. I just spent a couple weeks doing experiments with meshcore/meshtastic/reticulum/... comparing them to our stealth solution and I experienced a functional core in meshcore surrounded by a lot of vibe coded slop.

In particular I did not like the shoddy documentation of the various vibe coded interfaces and how brittle the integration experience felt because of them.

tiagod• 3 months ago

I came across this Andy Kirby guy on youtube, and his videos really came across as very sensationalized, exaggerated and clickbaity, which drew me away from meshcore, as I associated him with the project organization. This seems to validate my gut feeling.

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

Related Stories