Incessant tinkerer since the 70’s. Staunch privacy advocate. SelfHoster. Musician of mediocre talent. https://soundcloud.com/hood-poet-608190196

  • 3 Posts
  • 12 Comments
Joined 9 months ago
cake
Cake day: March 24th, 2025

help-circle

  • Hey, thanks for the back-check. I’m an expert at nothing. I know just enough to get by or when something might look super squirrely. The experiment was to see OP’s tool in action. I was just curious to see what would trigger a response. I wasn’t pitting the accuracy of AI against OP’s tool. I realize. even tho I use it, that AI can be inaccurate. Sometimes I’ll pit a few of them against each other to see how each interpret the data. I even use it when creating music. I am clinically deaf, and there are some frequencies I just can’t hear that well or at all. So I use AI in the mastering process. It’s just for fun. I’m not looking to break into the biz.





  • I share some of the same views you do about AI. I do use AI to help me with code. Not to develop and sell, just for my own personal use. So I tested out your ackchyually-ai. I had Grok create a docker compose to combine BorgBackup and BorgUI.

    Result:

    spoiler
    #########################
    # Services
    #########################
    services:
    
      # -------------------------------------------------
      #  Borg repository (data only)
      # -------------------------------------------------
      borg:
        image: ghcr.io/borgbackup/borg:latest
        container_name: borg_repo
        restart: always
        command: ["sleep", "infinity"]               # keep container alive
        volumes:
          - ./repo:/var/borg/repo                    # persistent repo
          - ./ssh:/root/.ssh:ro                     # optional SSH keys (read‑only)
        environment:
          # Uncomment if you want the repo to be encrypted by default
          # BORG_PASSPHRASE: "${BORG_PASSPHRASE}"
        networks:
          - backup_net
    
      # -------------------------------------------------
      #  Borgmatic – scheduled backup runner
      # -------------------------------------------------
      borgmatic:
        image: ghcr.io/borgmatic-collective/borgmatic:latest
        container_name: borgmatic
        restart: always
        depends_on:
          - borg
        volumes:
          - ./repo:/var/borg/repo                    # same repo as above
          - ./ssh:/root/.ssh:ro                     # SSH keys (read‑only)
          - ./borgmatic/config.yaml:/etc/borgmatic/config.yaml:ro
          - ./borgmatic/source_dirs:/source_dirs:ro # directories to back up
        environment:
          - BORG_PASSPHRASE=${BORG_PASSPHRASE}
        # Run borgmatic every day at 02:30 am using the built‑in cron of the image
        command: ["cron", "-f"]
        # If you prefer a host‑side cron, replace the command with “tail -f /dev/null”
        # and schedule `docker exec borgmatic borgmatic run` from the host.
        networks:
          - backup_net
    
      # -------------------------------------------------
      #  BorgWeb – Flask UI for browsing the repo
      # -------------------------------------------------
      borgweb:
        image: ghcr.io/borgbackup/borgweb:latest
        container_name: borgweb
        restart: always
        depends_on:
          - borg
        environment:
          - BORGWEB_REPO=/var/borg/repo
          - BORG_PASSPHRASE=${BORG_PASSPHRASE}
          # Optional basic‑auth (handled by the tiny built‑in Flask auth)
          - BORGWEB_BASIC_AUTH_USER=${BORGWEB_BASIC_AUTH_USER}
          - BORGWEB_BASIC_AUTH_PASS=${BORGWEB_BASIC_AUTH_PASS}
        volumes:
          - ./repo:/var/borg/repo
        # Expose the UI directly; you can map it to any host port you like.
        # 8080 = plain HTTP (for testing only)
        # 8443 = HTTPS if you put an external TLS terminator in front.
        ports:
          - "48443:8080"
        networks:
          - backup_net
    
      # -------------------------------------------------
      #  OPTIONAL: Minimal NGINX reverse‑proxy for TLS & auth
      #  (If you already have a front‑end proxy you can skip this block)
      # -------------------------------------------------
      nginx:
        image: nginx:alpine
        container_name: nginx_tls
        restart: always
        depends_on:
          - borgweb
        volumes:
          - ./nginx/nginx.conf:/etc/nginx/conf.d/default.conf:ro
          # If you have your own cert/key files, mount them here:
          # - ./certs/fullchain.pem:/etc/ssl/certs/fullchain.pem:ro
          # - ./certs/privkey.pem:/etc/ssl/private/privkey.pem:ro
        ports:
          - "443:443"
        networks:
          - backup_net
    

    Then I ran it through your checker.

    spoiler

    Results:

    Result breakdown

    Overall score

    This is entirely made up by ME, it’s not an official metric, so please don’t take it as gospel.

    There’s a lot of AI generated code here, it’s getting dangerously close to be sloppy. The ratio of comment to code is over 20%, this automatically pushes the score to 100% Comment ratio The amount of comments in AI generated code is borderline ridiculous. Comments are good, too many (often redundant) comments are just bloat.

    34 comments for 89 lines of code. That’s a ratio of 38%. The site assumes something is 100% AI generated if the ratio goes above 20%.

    Interesting that comment code was the trigger apparently. Personally, I comment a lot mainly because my brain is shit, so it’s very helpful. I haven’t run the docker compose, but I might just do that to see if AI came close. I’m sure some of the experts here would find the compose file to be wrong in some nature or another.


  • since spectrum is screwing them on price

    In my locale, Spectrum is considered a utility much like electricity, water, or any other utility you are accustomed to. They made it that way because a long while ago, Spectrum contracted with the authorities having jurisdiction, to be the sole provider of internet to all the schools in this area. There is a complaint form on our city’s webpage. Still, about the only way to make the pricing all work in your favor is to be the loudest complainer, which is a pretty shitty business model.