Recent submissions

Comment · 1 day ago
Unfortunately, this is going to be an everyday story. More and more bugs and breaches will be discovered and this move fast world more and more will be continued to be made.

Security is a perception, but right now it seems like it needs good PR.

Comment · 3 days ago
Thank you for that link. I started feeling rusty and needed something to shake off.

On a side note, I did founded my startup this year, and had that bug of doubt back of my head, but oh well…

Comment · 3 days ago
The dogfooding example I read was basically agent asking for user to sign off on permissions, Nd taking over from that point on. It doesn’t exactly read any different than any other ‘AI went rogue stories.

I am saying it’s a slippery slope and OIDC was not necessarily designed for it.

Comment · 4 days ago
I am only kidding, but if he would have used AI, or just said agents did it, in todays day and age he would be raising capital for his company.
Comment · 4 days ago
Ugh. OIDC’s whole trust model assumes the subject of the token is the responsible party. Sounds like you are opening a door for a future security problem.

OIDC is good when the end user needs short-term access validation and authorization. The claim and responsibilities of what they do are on that user. Now that you have agents involved, the user can just shrug it off, saying 'oh the AI went rogue'. You probably need a separate role for agent specific tasks that severely limits the access specific to your workload, but that is a work of its own.

Comment · 5 days ago
You should be more concerned about what comes next.

Either senior talent leaves, people who are close to retiring, or just can find a job easily outside.

Low hanging fruits take the bait and head out.

Mid level people live in fear of either scared to find another job, or worried about layoffs.

Either way the company morale is down the drain for a long time, and a culture is lost.

Comment · 11 days ago
I would love to see them move off into edge computing. There should be some autonomy and siloed experience in day to day usage.
Comment · 15 days ago
I have no words. Its like Elon asked Grok where can I take my business, and it suggested combine rockets and cars.
Comment · 1 month ago
Thanks for the reply. would that be against some GDPR policy, not that should be a concern in the beginning, but something to think about 'wipeouts'.

I struggled with deletion and clean ups a lot and found that is the hardest part to solve of it all.

Comment · 1 month ago
Comment · 1 month ago
I wrote this with a primary goal in mind to share facts and context across Agents.

It is open source and the way this works is by defining the typed memory around default predicates ex -https://github.com/Polign/recall/blob/main/internal/engine/d...

The predicates can be customized for individual use cases, and typed memory will extrapolate from the conversations you have with it. For example, in some use cases you should be able to deterministically separate actions from decisions. The agent, instead of guessing or hallucinating, will be able to successfully recall the precise decisions, and whether the actions are permitted or not.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton