Documentation for nanogram available here for awhile

Edit: Dont be a ungrateful. I put a lot of time, effort, and my own money into making this. I’m choosing to freely share it :)

Yes I get help from LLM’s. Review the code if you think it’s unsafe, or just move on and don’t use it. Happy to answer any technical questions.

Edit 2: Expanded source code for termux version here.

  • Ghoelian@piefed.social
    link
    fedilink
    English
    arrow-up
    18
    ·
    edit-2
    15 hours ago

    Apparently it was all ai generated and the author doesn’t actually know how to program. Just look at their responses in the .ml cross-post, that’s not someone whose software I would trust.

      • hereforawhile@lemmy.mlOP
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        2
        ·
        10 hours ago

        That’s wild that the mod thinks it’s off topic. Thanks for shareing that I didn’t even realize I had been censored by the mods.

    • 6nk06@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      8
      ·
      14 hours ago

      And it’s worse because they hide the Python code, which means that they can’t use tools like uv or ruff to check that everything works properly. I don’t understand why people do this.

      • CameronDev@programming.dev
        link
        fedilink
        English
        arrow-up
        3
        ·
        13 hours ago

        I dont understand why people do this

        Charitably: AI turbocharged dunning-kruger

        Less charitable: Malware delivery.

        There is no good reason why they couldn’t have a normal source tree, that they pack into a single shell script in CI.

          • CameronDev@programming.dev
            link
            fedilink
            English
            arrow-up
            2
            ·
            9 hours ago

            Sorry, but a photo of a directory structure is not a source tree.

            Your git repo consists of 4 files, a readme, a licence, and two packed shell scripts.

            If you have an actual published source repo, link people to it.

            • hereforawhile@lemmy.mlOP
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              8 hours ago

              So just a expanded file structure directory is what you want? The script executable expands to each individual piece once run.

              What do you mean a actual published source repo? I do not understand how its not that. Everything is packaged into one script.

              • CameronDev@programming.dev
                link
                fedilink
                English
                arrow-up
                4
                ·
                edit-2
                8 hours ago

                Yes. Separate out each part out. You are currently publishing the equivalent of of a compiled binary. Split it up, and use a script to “compile” it back into the mega shell script.

                It means that changes to each file can tracked (and audited) individually, you can conditionally compile bits in or out, and most usefully, you can write tests for the individual components.

      • Starfighter@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        13 hours ago

        Also the normal and rpi versions are two completely independent implementations of the same software. So now the LLMs have twice the maintenance load.

        I didn’t diff the two files but even the startup and control code appears to be custom for each version.

    • hereforawhile@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      10 hours ago

      AI generated I guess… with love, time, money, and care from me. Take it or leave it lol.