Hi folks. I have quite a bit on land with orchard of varies fruit aolive trees. I’m finding i would benefit from keeping a database of which tree gets what treatment, what fertilizer, how much produce i get, etc. Has anyone thought of such a tool? I use Joplin notes but its not as elegant, plus my sons are getting into it too now so multiuser woukd be cool.

  • JustEnoughDucks@slrpnk.net
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    3
    ·
    1 day ago

    “You’re right to push back, when you create a new plant layout on Fridays, it does drop the entire database and rm -rf / your system, would you like me to fix that for you?”

    • micgerne@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 hours ago

      "Here’s the updated script — it now correctly removes the french language localisation with rm -fr / "

    • MarauderIIC@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      5
      ·
      1 day ago

      Both not a likely problem with any recent model and absolutely mitigated by using it in a VM with snapshots, which, besides being good practice, is a technology that I expect selfhosters to be familiar with anyway.

      If there are objections to major models, (economic, resource, moral, etc), this application is achievable with a self-hosted Qwen or similar, although it will take additional nudging. That’s harder to get started with, though, which is why I didn’t suggest it. Self-hosted Gemma 4 I would absolutely recommend using in a VM, it really likes to erase projects and start over, in my experience.

      I hope that helps!

      • JustEnoughDucks@slrpnk.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 hours ago

        It was a joke, chill.

        But let’s be in good faith about this, vibe coders will overwhelmingly use cloud based corporate frontier models…

        And self hosting LLMs in general singularly and only solves one part of the resource objection (prompts running on green energy) and that is all and only if the model is run on green energy. It doesn’t solve most of the moral objections, IP objections, economic objections, resource objections, or brain damage objections.

        That being said, one’s own, local, never-to-release app or internal tooling is probably one of the better uses for LLMs like documentation discovery, informal document translation and tiny TTS and STT models (the best usecase in my own opinion)