I think there is also the case were companies will simply use different tiers for different tasks.
While the engineering team might need a cutting edge model (with the associated costs), the marketing department will be fine by something that can grammar correct or turn a few bullet points into prose. Likewise you already don't need Fable for Ticket -> RAG -> Reply with Faq knowledge or escalate workflows
That's already the case with other very expensive software like CAD packages were oftentimes you have different feature sets enabled for different employees.
I've met some people IRL who are so engulfed in their own greatness that it simply cannot be that they made a mistake (in planning and strategy). Therefore this is all a great injustice towards a poor victim and doesn't that sound like a great argument for some charity money.
Most of them grow out of it, some become politicians.
That is also not guaranteed. VW (with its array of brands) leads the european BEV market by a lot. [1] (sorry I only found data for April 2026 right now but earlier months were similar)
One additional point of data. In Q1 of this year they delivered 200K BEV worldwide [2] while Tesla did 350k [3].
Calling that 10 years behind is not warranted in my opinion. I would agree to say competitive and challenged.
Everybody should just assume that they are lying about data retention and learning anyway.
They showed zero respect for intellectual property in the past and they will show zero respect now or in the future. A few thousand Euros/dollars in subscription doesn't matter when several trillions are in play (at least in their plans).
Are they under any obligation to ground the value of their own stock or can a salesman simply claim that the "true" value of that stock is much much more than it currently seems to be?
Wrapper around the function call. Don't give it the token itself but a limited set of fixed functions to create domains (their use case according to the post).
Additionally give it a similar restricted way to "delete" domains while actually hiding them from you. If you are very paranoid throw in rate limits and/or further validation. Hard limits.
Yes this requires more code and consideration but well that's what the tools can be fully trusted with.
If you employ a new tech then there need to be extra safeguards beyond what you may deem necessary in an ideal world.
This is a well know possibility so they should have asked and/or verified token scope.
If it turns out that you can't hard scope it then either use a different provider, a wrapper you control (can't be too difficult if you only want to create and delete domains) or simply do not use llms for this for now.
Maybe the tech isn't there just yet even if it would be really convenient. It's plenty useful in many other situations.
> The problem here is taking "word for word" as "by dictionary meaning", which is never how laws are read.
Back in the days of "smart contracts" and "DAOS" this was something many well-meaning technical people struggeled with. Humans and their societies are flexible and therefore laws must be flexible as well (to a certain degree before it becomes damaging).
It's also why a lawyer/expert is usually recommended when engaged with legal matters: We as layman lack all the context around seemingly "simple" concepts, procedures and definitions. You can learn all of that or hire a professional.