**#A quick edit to address something important and provide a disclaimer: **

Thank you all for your feedback! This project was “vibecoded” with Cloude AI and serves more as a “proof of concept” for what could be achieved with AI assistance. I’m just a tech enthusiast, and I’m excited to continue exploring new possibilities. I understand there’s a real concern about “AI Slop,” but that’s exactly why I’m sharing this project with you all so that experts who are interested in the idea can offer guidance or even help improve it.

I’ve noticed that many people with home labs prefer to update their applications manually instead of relying on other apps that automate the process. Often, they have to check each one individually. That’s where Vigil comes in. The primary function of Vigil is to centralize the information and give users clear visibility of which applications are outdated, their current version, and the newer version available from several sources. This way, you can decide what and when to update.

To be honest, I hope it ends up being useful to others as it is for me.

If you have a few minutes, I’d really appreciate you trying it out and leaving a review or suggestions on the repo or even here. I’d do my best to answer most of the comments.

REPO: https://github.com/kumucode/vigil.git

  • 1step@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    23 hours ago

    Absolutelly vibecoding it with Cloude. I understand a bit of python and html but I’m no dev or technical professional at all. I just wanted to see if I could build something useful without much of technical expertise.

    • markko@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      19 hours ago

      I appreciate you being honest in your response here.

      I’d recommend adding this disclaimer to the post text and repo readme for complete transparency, and so anyone who doesn’t want to use AI-generated projects can move on without creating arguments in the comments.

      There are many genuine reasons to not trust code generated by LLMs, especially with anything network-connected or handling important data, so it’s important to be upfront about it.

      • 1step@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours ago

        Hi markko, you’re right, adding a tag would certainly lower expectations and give more clarity to projects. I’ll add this on the post and to the repo.

    • ramielrowe@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      19 hours ago

      EDIT: removing this comment because I don’t think you will use this feedback responsibly

      • 1step@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        22 hours ago

        Hi @ramielrowe thanks for the feedback, that’s actually pretty good and I’ll start using it. I understand that all this AI thing can be sloppy, and create more friction than good, but I’m really fascinated by how it can help people with little knowledge to build something that a few years ago would’ve been only possible by experts.

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          for a very long time it was not only possible for experts. like, I would say the last 10-15 years, maybe even more. It’s very harmful that people can now create things they don’t even know how to check what it does, and they just assume this “sentient thing” actually produced what you wanted with no major flaws. thing is, you (or anyone else vibecoding things) won’t be able to determine what is good or bad without taking the time and learning the building blocks, learning how they work and how they are supposed to be used.

          also your comments look like AI generated comments, fake enthusiasm and all the rest. it does not inspire much confidence