• 2 Posts
  • 128 Comments
Joined 2 years ago
cake
Cake day: September 25th, 2023

help-circle






  • The user can choose whether the AI can run commands on its own or ask first.

    That implies the user understands every single code with every single parameters. That’s impossible even for experience programmers, here is an example :

    rm *filename

    versus

    rm * filename

    where a single character makes the entire difference between deleting all files ending up with filename rather than all files in the current directory and also the file named filename.

    Of course here you will spot it because you’ve been primed for it. In a normal workflow, with pressure, then it’s totally different.

    Also IMHO more importantly if you watch the video ~7min the clarified the expected the “agent” to stick to the project directory, not to be able to go “out” of it. They were obviously painfully wrong but it would have been a reasonable assumption.









  • Do you have a specific use case for two containers that you want to talk to each other?

    Sure, for example once a Jitsi Meet meeting ends (more than 1 person in a room in, everybody gone), save the chat log to CopyParty e.g. WebDAV push to /meetingname_date.txt would be enough to be useful. It’s something we tend to do manually on a regular basis.

    road map of what you are trying to accomplish before hand, and run it by the dev teams.

    Yes no rush and I can code so I would be able to test before suggesting anything.

    As I’m thinking about it, I wonder if your solution might be automation?

    I don’t touch AI but I do think conventions, e.g. not “just” an API but SWAGGER, specific filesystem on mountpoints, etc could facilitate this.



  • Thanks, that’s indeed exactly the kind of thing I’m looking for “The authentication glue you need.” but even more generalized than that, e.g. just “the glue you need.” not solely for authentication.

    Edit: to clarify and coming back after leaving few other comments, the 1 thing authentik has is that it is a cross-service need, namely nearly all services do need authentication AND, probably consequence of that, there are conventions and standards already in place, e.g. SAML, OAuth2/OIDC, LDAP, Auth0. So that makes everything much easier.