• shortwavesurfer@lemmy.zip
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    18 days ago

    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.

    • KryptonBlur@slrpnk.net
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      17 days ago

      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.

      • shortwavesurfer@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        17 days 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.

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    18 days ago

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

    • hendrik@palaver.p3x.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      18 days 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.