🤣 sure, I’ll use a reverse proxy / waf that has a release change log “I don’t remember lol” (Yes, it’s in alpha, but still…)

Is anyone here using it? Are you scared?

  • paris@lemmy.blahaj.zoneEnglish
    9·
    13 hours ago

    Almost every single deployment has failed lmao

    https://github.com/netgoat-xyz/netgoat/deployments

    Edit:

    Oh my god they’re committing their .env with their “DiamondKey” (different from their API_STREAM_KEY) and they’ve committed TWO .exe files named agent.exe and agent.exe~. They’re also looking for strategic partnerships who should reach out via Discord(???) and Gmail. Their quickstart includes only two things: a link to unpublished docs and the sentence “We recommend datalix for cheap and highly avaliable [sic] vps’ses [sic]” (no closing punctuation like a period, despite that being common throughout the readme). You can tell very obviously which parts were written by the person behind this project and which were generated by an LLM.

    Edit 2:

    Their 1.0.1-alpha.1 - Syncronizing [sic] versioning - Minor Changes commit rewrites like the entire project??? Very obviously an ai slop project by some teenager who had an idea far beyond their skill level and decided to use ai instead of building up their skills over several years and changing the scope of their project to be a building block towards their idea that helps them develop the knowledge they would actually need to develop a project like this. They’ll realize at some point that they’re in over their head and that fancy code generators don’t magically fix that; I’d be surprised if this project is still being worked on by the end of the year.

    • dont@lemmy.worldOPEnglish
      1·
      3 hours ago

      Thanks for the analysis; I had also seen the API keys, but I didn’t check the deployments.

      I guess this answers my question then: No one is using it because not even the dev gets it deployed – highly “avaliable” 🤣

  • hendrik@palaver.p3x.deEnglish
    51·
    2 days ago

    After a few “Delete junk” commits, “Broken”, “PATCH: Hope this fixes it”, and “Basic Reverse-Proxy”, it’s now at version 1.0.1-alpha.1.
    Don’t know what they did to Git. But their “minor commit” touches almost the entire code in their repo. Rest of it (and the general confusion and the edgy commit messages) look to me like something done by OpenClaw.

    100% wouldn’t use it.

  • SavvyWolf@pawb.socialEnglish
    29·
    2 days ago

    Is this an allegedly “high performance” reverse proxy written in NodeJS? Uh… Yeah, good luck with that.

    Also, how do they intend to protect against DDos attacks in a self-hosted environment with (presumably) a limited number of devices?

    • dont@lemmy.worldOPEnglish
      4·
      2 days ago

      To be fair, the proxy engine is supposedly written in go, not in nodejs, but yeah, the ddos defense most likely is wishful thinking…

      • Cloudstash@lemmy.worldEnglish
        1·
        18 hours ago

        Pretty much always overratee if it happens on the same line. Just change methods and fk it up.

      • jj4211@lemmy.worldEnglish
        3·
        2 days ago

        Of course I also see that the go spawns python and does stuff with that…

        And there’s lots of other dubious issues that look like an odd mismash of intro level programming stuff with unfortunate performance implications, and a very strong vibe code smell, though the commit interval is a bit larger than I would have presumed with vibe coding, but the volume of changes seem AI sloppy…

        Well, broadly it looks like slop, probably AI slop, but either way I wouldn’t go anywhere near this project…