> I added Helen to my roster just this week.

yeah. cringe. I debate with myself is this Aghata can truly be trusted to be > I need to find the secret traveling farther than it should, the data leaking where it shouldn’t, the assumption I made that an attacker won’t make. I need to be paranoid on behalf of the users whose data and trust I’m protecting.

at the end of the day its still an llm. but hey, I want to call Claude _Claudius_ all the time but I don't cause it'll shut me down real quick

When Copilot was first released I called it Bing and it got mad. :P

I read this yesterday and then came back today to upvote and comment because I thought it was so beautifully said

Pure poetry. Loved it. Hits the nail right on the head

Just don’t use the eval features, inline scripts and properly sanitise user input (if any) and you will mitigate all these issues

I feel like a more effective way to use cron is just to dispatch jobs into a queue that will perform the actual processing. And not to do the processing within the cron scripts themselves. That way the load on the cron is light and the heavy lifting is done by your queue/worker system.

This works great in my experience.

A lifetime ago I scaled up cron jobs for a client with Gearman. Using cron to trigger jobs on the Gearman server and the pool of runners to do all the work. This proved to be so reliable they still use the system today, over 10 years later.

Really cool! For the Gearman workers, did you load jobs dynamically? Or, would you have to re-deploy for new jobs/updated jobs?

As I recall, all the jobs are checked into a repo that is deployed to all the runners, which each start gearman workers for their assigned role.