Hacker Newsnew | past | comments | ask | show | jobs | submit | sofixa's commentslogin

I think the only solution to this kind of challenge is forcing the agent to go through a proxy which handles all the authentication and authorization for the agent (thus it never has too much access to abuse), and monitors for exfiltration or prompt injections.

> Anthropic won enterprise

Depends on the enterprise, Mistral are pretty big here in EMEA because they're more trustworthy and you can self-host. Self-hosting ensures you can control costs better, fine tune the models for your own funky whatever (e.g. Ericsson fine tuned models to understand and run in their their custom silicon) but most of all, that your data remains where it needs to be.

My bet is that this kind of enterprise deployment with customisation is where the real big money in AI is (and not coding assistants), but it will mostly be spent by the big banks, industrial giants and SAPs of the world, who will want control.


Nope. Even if you don't trust the reporting and information coming out of Russia, it's pretty self-evident that Russia thought they won't have much of a war to fight. Half of the attack on Kyiv was done by Rosgvardia (riot police), with parade gear and musical instruments in their logistics.

You don't do that if you think you'll have a quick victory, you do that if you're certain there will barely be any war.


> For the US and friends is terrorizing the enemy, his forces, his civilian population into giving up

The US has tried to do it a few times (most notably Vietnam), but it isn't the strategy in the slightest. The goal is always an Iraq style campaign with heavy air attacks to destroy/confuse most enemy capabilities before a swift invasion.

Terrorising the population in submission has never worked. The US Air Force's own study of strategic air power after WW2 concluded so.

> That’s absolutely not what’s missing in Ukraine

> and then push forward with your own armour

If you rule the skies, you shoot down most attacking drones / it becomes too dangerous to launch drones from short to medium distances (because you'd be found out and destroyed ASAP). It's important to remember that not all wars are the same, and a competent army from a strong military power wouldn't have gotten bogged down to trenches in the first place. Mobile warfare is all about speed and unpredictability and the enemy being unable to react in time


You establish air superiority first by doing supression of enemy air defences, then destroying any offensive capabilities they might have (air bases, fighters), and then you rule the skies.

This didn't work with Vietnam nor Afghanistan.. and US had 100% superiority.

Yes, it did. Over both of those the US had, mostly, control of the skies.

Hanoi had extremely heavy air defences and was left mostly alone (both because of that and because it wasn't considered a politically appropriate target).


Yes, but the point about Napoleon is that there was so much more about him than just military talents. The environment in which he flourished wasn't of his making, but he managed to grow in it and ended up impacting the whole world. Either directly by bringing the Napoleonic legal system to them with an army, or indirectly by inspiring or enabling nationalism, democratic ideas (power coming from the people, not deity), allowing the whole of Latin America to break free from the Spanish Empire by keeping the latter busy, etc etc.

Many people became successful militarily and even seized power afterwards during tumultuous times. Very few actually ended having such an impact worldwide.

And before any Brits come in with centuries old grudges, of course he did plenty of bad, most notably how he treated Haiti (which he at least acknowledged later in life).


Ah, yeah, he almost strangled Britain with his Continental Blockade. Would probably have been his greatest gift to the world, if he actually managed to pull this off. Oh well.

Did you read even a summary of the AI Act?

The gist of it is very simple - depending on the risk of what you're doing with AI, you have to document why it did what it did, and be able to explain it; or you can't use it at all. So if you're using AI for mass surveillance, you can't; if you're using it for treating loan applications you need to be able to explain why it approved/denied; if it's a customer service chatbot, do whatever, nobody cares.

Not only is burden of the legislation fairly low (and a lot of it hasn't come into force yet), it is extremely reasonable. No, sorry, we don't want a UnitedHealthcare using a broken algorithm on purpose to deny as much care as possible and hiding behind computer says no.


> This is a race and nobody will care or remember how the winners got there.

For consumer AI, yes. For coding assistants, probably.

For specific application "business" AI like the things Airbus announced the other day? Not at all. What matters for an Airbus using Mistral to build compliance documentation based on AI generated physics simulations is the enterprise relationship, reliability, compliance, forward deployed engineers helping with the fine tuning, quality, predictability, support. A Chinese lab having a better at benchmarks model that is cheaper is just irrelevant for that.

And IMO, the real money in AI is this type of "business AI" deployment. Developer tooling tends to converge on becoming commoditised. Once you're a core supplier for a big bank and embedded in their processes, you're there untill you screw up with the pricing (like Broadcom), and even then.


> I am wondering what is keeping them back, though: Money? Compute? Skills? Training data?

Considering all their talk about new DCs and compute, and a few offhand comments, it sounded to me that compute is a big limitation.


> So the current situation is basically that I used Claude to write an MCP server on top of our API. And then I need to occasionally tell it update it match the public doc.

> And my reaction is: really? It is not like our API docs are not public. Claude Code created our MCP server with zero instructions beyond what is publicly available. I just told it to read the docs from the net.

My reaction to this is.. really? Presumably your API and API docs have a release process. Hopefully an automated one. Why isn't the "hey Claude, update the MCP server" step a part of it?


That wouldn't solve the core issue: if Claude makes a mistake during the MCP generaration, it would poison further agentic use.

It's adding another failure point to the process for no gain.


No, because as everything which is a part of a release process, you'd have tests.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: