[–] 1 point 1 month ago*

While you can, there has been research that showed that the LLMs answers can be influenced by the order in which the possible options are presented.

I haven't looked into how these "System One" "Noul" models (absolutely stupid nomenclature imo) work but the hope would be that theyre less susceptible to such problems.

  • source
  • parent
  • context
  • [–] 4 points 1 month ago (1 child)

    The thing is sounding rockets do exactly that and are still in service (vs somehow unfucking an ancient plane that hasn't been serviced in decades with tooling that no longer exists) and there are multiple companies out there operating supersonic drones for high speed tests of whatever you wanna do.

    I dont see the value in bringing the blackbird back into service. I think its more likely that they want to freshen up the paint and park it at some press conference / event.

  • source
  • parent
  • context
  • [–] 5 points 1 month ago* (2 children)

    A little over 20 mins:

    Splashdown in the western Atlantic at 24.25° N, 70.00° W, 4.9 km from the target point, occurred at 8:59:35 a.m. EST. The crew was picked up by helicopter and brought to the U.S.S. Guam at 9:23 a.m. and the spacecraft was recovered at 9:58 a.m.

    Source

  • source
  • parent
  • context
  • Authentik Helm woes (discuss.tchncs.de)
     

    I'm currently in the long process of rebuilding my declarative homelab using k3s, ArgoCD and NixOS.

    I had previously used Keycloak but that always seemed massively overqualified and way too complex for my purposes. With this rebuild I saw my chance to try out Authentik which appears to be in good standing with the homelab community.
    They have tons of documentation for pretty much anything which was encouraging to me. Well except for the documentation for their Helm Charts maybe...

    Started off with version 2025.12.x, am now onto 2026.02.x and have spent most weekends in between that on getting Authentik to even just deploy to the cluster.
    It's partially my fault for attempting to use Secrets initially but even now with hardcoded keys in my git repo the default example chart doesn't work:

    values.yaml

    authentik:
      existingSecret:
        secretName: authentik-secret
    
      postgresql: # None of this gets applied at all so I do it manually below...
        password: "somepasswd"
    
    server:
      replicas: 1
    
      env: # Manually apply all the configuration values. Why am I using Helm charts again?
        - name: AUTHENTIK_POSTGRESQL__HOST
          value: authentik-postgresql
        - name: AUTHENTIK_POSTGRESQL__USER
          value: authentik
        - name: AUTHENTIK_POSTGRESQL__PASSWORD
          value: "somepasswd"
        - name: AUTHENTIK_POSTGRESQL__NAME
          value: authentik
    
      route:
        main:
          # ...
    
    postgresql:
      enabled: true
    
      auth: # And set everything here once again
        username: authentik
        password: "somepasswd"
        postgresPassword: "somepasswd"
        usePasswordFiles: false
        database: authentik
    
      primary:
        persistence:
          size: 4Gi
    

    I started off with the official example and after all these undocumented changes it still only deploys-ish:

    With the defaults authentik-server would always try to reach the DB under localhost which doesn't work in the context of this chart/k8s.
    So after a while I figured out that the authentik: configuration block doesn't actually do anything and I set all the values the chart should set by hand.

    Now the DB connects but the liveliness probe on the authentik-server pod fails. It logs the incoming probe requests but apparently doesn't answer them (correctly) leading to k8s killing the pod.

    Sorry for the ramble but I've hit my motivational breaking point with Authentik.
    Since the community seems to like it a bit I am left wondering what I'm doing wrong to have this many issues with it.

    Did you people have this much trouble with Authentik and what have you switched to instead?

     

    cross-posted from: https://lemmy.ml/post/36210816

    asciinema (aka asciinema CLI or asciinema recorder) is a command-line tool for recording and live streaming terminal sessions.

    This is a complete rewrite of asciinema in Rust, upgrading the recording file format, introducing terminal live streaming, and bringing numerous improvements across the board.

    view more: next ›