Live data from Hacker News

“Too dangerous to release” or just too expensive?

kingy.ai

51–60 of 189 posts

Re: “Too dangerous to release” or just too expensive?

#51

The thought of this didn't even cross my mind until yesterday. I previously figured the hype was primarily around marketing, but after watching this Primagen video, I have the same suspicion. https://www.youtube.com/watch?v=zaGOKd4jqEk

Is it possible that curl just doesn't have any critical security vulnerabilities left?

Re: “Too dangerous to release” or just too expensive?

#53
(I work at Anthropic) We have publicly stated[1] that our goal is to deploy Mythos-class models at scale when we have the requisite safeguards for offensive cyber risks in place. Mythos is a general frontier model, not a cyber-specific model so there are many reasons why we think our users will benefit from access (with the aforementioned safeguards in place) in due course. Compute has also not factored into our decision[2] to rollout the model in a limited fashion to defenders. We'll be sharing more soon on the first month or so of the project and rollout.

[1] https://www.anthropic.com/glasswing#:~:text=deploy%20Mythos%...

[2] https://x.com/logangraham/status/2054613618168082935

Re: “Too dangerous to release” or just too expensive?

#54
post #18

My thinking is that if it really was super duper then Anthropic could charge eye watering amounts and have willing customers and set up expectations going forward that SOTA costs a lot to use. That they don’t suggests that really it is only incrementally better than Opus 4.7 and that the market won’t bear a price increase that makes it economical to serve let alone profit from serving. So the cynical me imagines exec…

They announced the pricing when they released preview: $25/$125 per million input/output tokens. I have no doubt they're already selling it to select customers.

They are. Mythos Preview is not free.

Re: “Too dangerous to release” or just too expensive?

#57
post #3

> Resource Limit Is Reached The website is temporarily unable to service your request as it exceeded resource limit. Please try again later. I guess it was too dangerous to even read the article

archived: https://nonogra.ph/too-dangerous-to-release-or-just-too-expe...

Re: “Too dangerous to release” or just too expensive?

#58

When your logo is AI, your illustrations are AI, and you profile pic is AI, I'm going to assume the text is AI too and won't read it.

Now imagine that your work specs are generated by an AI agent that the EM is using. Do you still care about the work?

Brother, I don't care who writes the specs as long as they sign the checks on time. And yes, I do care about my work even if upstream is slop. In a relay race, you can lower your performance to weakest leg, or you can be the strongest leg. And maybe I just like to run.

Re: “Too dangerous to release” or just too expensive?

#60
post #42
post #31

My posts* got to the first spot on hackernews couple of times. Never once it broke down like that. And why would it, it's just a bunch of html and css files served through (free) vercel (don't think it matters). I wonder what do people run their blogs these days, so they fail under the pressure so easily. * https://news.ycombinator.com/from?site=yanist.com

It's WordPress, which is a great CMS but can quickly crumble under load when using cheap hosting.

With an external cache/CDN it should work perfectly fine.

There are also some caching plugins for wordpress, but most of them still hit the database on every request.

Post reply on HN