Comment by matheusmoreira
2 hours ago
For reference, here's what my experience with Fable turned out to be like:
https://news.ycombinator.com/item?id=48466313
Just a code review of my own project. Downgraded to Opus 50% of the time while evaluating the critical I/O and memory safety parts, the exact thing I wanted it to do.
And now it's gonna be even worse.
I mean what do you expect when covering memory safety topics with a model that's not allowed to cover security topics? This seems totally expected. It'll be the same when 5.6 is released.
> what do you expect
I expect the strong cybersecurity model to help me strengthen the cybersecurity of my project.
> not allowed to cover security topics
They said it wouldn't be usable for offensive purposes. This is the opposite of that.
You don't have the strong cybersecurity model. That is not Fable. It never was, even at release.
The cybersecurity model is Mythos, which was never made publicly available. It is only available to a list of US government approved companies.
> They said it wouldn't be usable for offensive purposes
No, they said Fable would refuse for cybersecurity and offensive purposes. You are conflating Fable with Mythos.
1 reply →
Is there a difference though?
Fable 5, harden my openssl project. Then you use the diffs/summary to find out what the bug is for your exploit.