1,298 karma · joined February 11, 2020
I get it, the API key was my responsibility, but, setting the dollar limit is exactly the guard they suggest against that.
On top of that, near as I can tell, there are no protections for your API key. No restrictions by country, IP, etc...
If China is ok with open models being open... they will be. An attacker isn't going to be deterred by a US law saying they can't use them.
I guess my point is that if China is ok with open models, then, the attackers will have them regardless of any laws in other countries. Restricting them, in that case, doesn't seem to accomplish much?
It’s expensive, and not as capable as the frontier models, but would have some pretty big benefits around privacy and agency.
Do you have an example of how this is how they have advertised or sold the plan? I don’t recall ever seeing any advertisement that their plan is simply pre paying for tokens.
What percentage of your interaction do you want/think is actually real people, and not just agents talking to other agents?
"Dear Claude, please make me a clone of <fancy new saas> but make <these changes specific to my tastes>".
For many things, it's probably not "select the one of 100 that fits my taste", it's probably going to be to just make your own personal version that fits your taste in the first place. And, probably, never share that anywhere.
Yesterday "I don't know about you, but I benefit so much from using Claude at work that I would gladly pay $1,500-$2,000 per month to keep using it."
If I launch a new product, and 4 hours later competitors pop up, then there's not enough time for network effects or lockin.
I'm guessing what is really going to be needed is something that can't be just copied. Non-public data, business contracts, something outside of software.
I wonder what the security teams at companies that use StrongDM will think about this.
"Impact statement: As early as 19:46 UTC on 2 February 2026, we are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs) across multiple regions. These issues are also causing impact to services with dependencies on these service management operations - including Azure Arc Enabled Servers, Azure Batch, Azure DevOps, Azure Load Testing, and GitHub. For details on the latter, please see https://www.githubstatus.com."
Feel free to ignore this, but, what's your long term plan here? I see you have Enterprise plans (especially that allow different licenses). From what I can tell you're the only contributor, but, I assume that if you accepted contributions there'd be a CLA?
I see "Multi Agent Orchestration", but, scrolling through this I still have no idea what I'm looking at.
Also, I'd guess, the sort of people who are comfortable with asking an LLM to build the premium features are, uh, morally flexible enough to not care about licenses in the first place.
Obviously, SSO is the best choice for most deployments. Enterprises (who will probably pay the most) will require SSO.
Open Source is the "free taste". Everyone knows, uses, and likes Grafana. When your company is looking for something, you'll recommend it because you're familiar with it. Your company will want things like SCIM or similar, and pay them for it.
It's harder for products that are trying to sell to smaller companies/individuals, but it still applies.