Migrating to the new meshcore.io site

Drama happening at Meshcore.

all 5 comments

sorted by: hot top controversial new old
[–] 15 points 6 months ago* (2 children)

I'd say the only thing wrong with this is that they explicitly said that the Liam Cottle app is the official app, even though it's closed source proprietary shitware, and I personally will not touch it due to the fact that meshcore-open exists. Quite frankly, Andy can go get fucked. I never did care for his better-than-thou attitude.

  • source
  • hideshow 2 child comments
  • [–] 6 points 6 months ago (1 child)

    Yeah I'm sticking to meshtastic honestly. I know its routing in urban areas isn't as good, but at least it's fully open.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 6 months ago

    The main project of meshcore is open, and the meshcore-open app is open, but you do have to be careful because there are some firmware variants for devices such as the TDECK that are not open.

    As long as I'm capable of using it in a completely open way, I'm fine with it. I just don't have to touch the proprietary bits.

  • source
  • parent
  • [–] 6 points 6 months ago (1 child)

    We ran a poll recently, and asked in the MeshCore Discord about AI and trust, and these are the results

    I don't quite understand the "trust" issue with AI code. Well - I kinda do but it's overblown.

    Trust is not about having people vs. robots. It's about having good code review and transparency. It's a process thing not a "who wrote this" thing.

    If you're running an open source project you need to be putting those guardrails in place anyway, unless you want to end up with an XZ Utils-like backdoor in your project (which required no AI to do).

  • source
  • hideshow 1 child comment
  • [–] 4 points 6 months ago* (last edited 6 months ago)

    I have a hunch how that might just not happen. If it's a singular developer pumping out all kinds of features, websites, software... There's a good chance there's little oversight nor any proper guardrails in place.

    So hypothetically, sure?! In practice I also see how some things sometimes go hand in hand. And you better check who writes and maintains your software, if you're planing to use it long term. At least that's what I've seen. Once a project is mostly vibe-coded, there's automatically a high chance there's weird things going on. Or I'll write something to the issue tracker and there's nobody there. Or maintenance stops after a week because they vibe-code the next thing... So I'm a bit wary. I guess because in reality lots of people don't use these tools responsibly.

  • source
  • parent
  • 14 comments in c/technology@lemmy.world view that post
    [–] 24 points 6 months ago (4 children)

    what a mess. first meshtastic vs meshcore and now meshtastic, meshcore and meshcore-but-different-devs

  • source
  • hideshow 4 child comments
  • [–] 11 points 6 months ago (3 children)

    TLDR: Stick to the open source Meshtastic?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 17 points 6 months ago

    I love meshcore, have a repeater and im building out my local mesh - such a shame about andy overstepping and slopping such an important thing - thanks for this psa

    Genuinely decentralized and resilient communication is fundamental to individuality and resistence against authority - for andy to try and assert himself and coopt larger authorities into this is frankly disgusting and i appreciate the explicit splitting off from him - hes acting dangerously wether he knows it or not.

  • source
  • [–] 15 points 6 months ago

    They did put out that the official app was the Liam Cottle one which is closed source and so I won't use that particular app because I don't use closed source software when I can avoid it. The only one I'll use is meshcore-open. Quite frankly, Andy can go get fucked. I never did care for his better-than-thou attitude.

  • source
  • [–] 15 points 6 months ago

    So Andy was the reason for the split from Meshtastic and now the split of Meshcore. Sounds like Andy is the problem. Glad the other devs are taking a stand against vibe coded slop.

  • source
  • [–] 8 points 6 months ago* (last edited 6 months ago)

    I'm very surprised that Andy's claim to the MeshCore trademark is at all valid, considering the project has existed before he got involved

    EDIT: Dug around a bit, and the trademark claim is currently "Pending"

  • source
  • [–] 15 points 6 months ago (1 child)

    Unironically sickening to see the "real uses" of AI. Fuck community and cooperation, all you need is a subscription and narcissism

  • source
  • hideshow 1 child comment
  • [–] 6 points 6 months ago

    Can't tell if this "Andy" Character is a narcissist, a fed, or both. Because if neither? That blog post would be legally actionable.

    I don't mind AI-generated code, so long as its human audited to prevent slop bullshit from going awry. I dunno if I trust Andy like that after seeing this behavior.

  • source
  • [–] 4 points 6 months ago (1 child)

    I'm new to mesh and have some radios on meshtastic, but none on meshcore, yet.

    Help me understand the implications of this. Does this mean people will have to reflash existing infastructure to ensure they're on whatever fork/branch ends up favored by the community? Will it split the community geographically?

  • source
  • hideshow 1 child comment