jmogly

He definitely is doing it for the love of the game. Different generation loves to work

I watched my 75 year old human plumber (who sniped a guy his first day in vietnam), kneel on two 3 inch wide joists and drill a 4 inch diameter hole at a 89 degree angle through said joists. Where’s the robot that does all that?

Above from all the other doomer crap in this article, I find the job replacement rhetoric the most offensive. It is always people that are so detached from the reality of labor, people who’s only “job” has been to essentially have ideas and opinions.

or, just let people call things what they want, and focus on real problems instead. Even this comment as I’m typing feels like too much time committed to the subject.

I got the feeling watching that last season of Stranger Things that the storyline and some of the dialogue felt AI generated. It sucked by the way.

Yes I suppose this is the bare minimum, but isn’t that just a nasty way to go about things? What about responsibility and decency, do we just not do that anymore?

How do you know that the llm is correctly translating the english queries to the verifiable primitives? It seems like it’s just pushing the problem to another layer?

Ah yes great point, awesome article by the way —- thought provoking, shocking, really crazy stuff. Hopefully some good comes of it, godspeed.

It is kind of a fundamental risk of IMDS, the guest vms often need some metadata about themselves, the host has it. A hardened, network gapped service running host side is acceptable, possibly the best solution. I think the issue is if your IMDS is fat and vulnerable, which this article kind of alludes to.

There’s also the fact that azure’s implementation doesn’t require auth so it’s very vulnerable to SSRF

Mainly for getting managed-identity access tokens for Azure APIs. In AWS you can call it to get temporary credentials for the EC2’s attached IAM role. In both cases - you use IMDS to get tokens/creds for identity/access management.

Client libraries usually abstract away the need to call IMDS directly by calling it for you.

This is insane, when you say azure OpenAI, do you mean like github copilot, microsoft copilot, hitting openai’s api, or some openai llm hosted on azure offering that you hit through azure? This is some real wild west crap!

Haha, you can already see wheel reinventors in this thread starting to spin their reinvention wheels. Nice stuff, I run my agents in containers.

OP never mentioned letting the agent run as him or use his secrets. All of the issues you mention can be solved by giving the agent it’s own set of secrets or using basic file permissions, which are table stakes.

Back to the MCP debate, in a world where most web apis have a schema endpoint, their own authentication and authorization mechanisms, and in many instances easy to install clients in the form of CLIs … why do we need a new protocol, a new server, a new whatever. KISS