🤣 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?

  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    19
    ·
    9 hours 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.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 hours 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…

      • jj4211@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours 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…

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    39
    ·
    edit-2
    11 hours 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.