When high quality effort is applied to a tool, such as AES or the linux kernel, we intuit that it "hardens" the tool. That is, it makes the tool more correct, more resilient, less assailable, etc. Similarly, when effort is applied to an open problem, such as the Riemann hypothesis or P v NP, without progress, it "hardens" the problem: it makes the problem feel more daunting to whoever takes a stab at it next. Andrew…
Discovering Cryptographic Weaknesses with Claude
111–120 of 199 posts
Re: Discovering Cryptographic Weaknesses with Claude
#112Earlier quoted context omitted.
How often I do it doesn't matter because it's such a trivial thing to switch. If you're gonna "try it for a few weeks" the part of you that has to learn the typing-specific parts of that method is about 1% of the difficulty. It's really easy to ignore typos. And the way you have to approach thinking and correcting is the same whether you're typing or voicing. If you can't just type the way you would just talk, and yo…
But it's literally not. You already correct yourself and revise your speech in an append-only rolling edit. You do it all day every day for decades. Versus never writing in this way. Have you tried the voice-based prompting, as I'm describing?
> Have you tried the voice-based prompting, as I'm describing?
I've never prompted a thing. I can just see your distinction is nonsense. If you think it's hard you're doing it wrong.
And wow I did that post without revising a thing. Wow.
Re: Discovering Cryptographic Weaknesses with Claude
#113Earlier quoted context omitted.
Been skeptical for quite some time that "using AI" is a real skill/genuine field of expertise. I think I need to start sharing that skepticism more loudly and publicly! (I'll caveat that by saying I think machine learning fundamentals are useful for evaluating any estimator. And an ML background can be good to give one an appreciation of how hard some tasks are to estimate, such as machine translation, summarization,…
I think knowing what you want (and being able to articulate it with adequate specificity, and detecting when processes drift away from it) is a real skill/field of expertise. I just don't think it's specific to interfacing with "AI."
Re: Discovering Cryptographic Weaknesses with Claude
#114Earlier quoted context omitted.
Been skeptical for quite some time that "using AI" is a real skill/genuine field of expertise. I think I need to start sharing that skepticism more loudly and publicly! (I'll caveat that by saying I think machine learning fundamentals are useful for evaluating any estimator. And an ML background can be good to give one an appreciation of how hard some tasks are to estimate, such as machine translation, summarization,…
I think knowing what you want (and being able to articulate it with adequate specificity, and detecting when processes drift away from it) is a real skill/field of expertise. I just don't think it's specific to interfacing with "AI."
Re: Discovering Cryptographic Weaknesses with Claude
#115Earlier quoted context omitted.
But it's literally not. You already correct yourself and revise your speech in an append-only rolling edit. You do it all day every day for decades. Versus never writing in this way. Have you tried the voice-based prompting, as I'm describing?
"never" schmever. I never ramble unrestrained either. Deciding not to edit at all is a skill either way. If you just want the equivalent of voice in a normal way, you remove backspace and that's it. > Have you tried the voice-based prompting, as I'm describing? I've never prompted a thing. I can just see your distinction is nonsense. If you think it's hard you're doing it wrong. And wow I did that post without revisi…
Sheesh, imagine thinking you choose not to rewind time and "edit" the speech that has already come out of your mouth lmao.
Re: Discovering Cryptographic Weaknesses with Claude
#116Earlier quoted context omitted.
"never" schmever. I never ramble unrestrained either. Deciding not to edit at all is a skill either way. If you just want the equivalent of voice in a normal way, you remove backspace and that's it. > Have you tried the voice-based prompting, as I'm describing? I've never prompted a thing. I can just see your distinction is nonsense. If you think it's hard you're doing it wrong. And wow I did that post without revisi…
Right. So the crux of the issue here is you have no experience with what's being discussed, while I do. Sheesh, imagine thinking you choose not to rewind time and "edit" the speech that has already come out of your mouth lmao.
What experience do you insist I'm lacking in something I'm doing right now?
Re: Discovering Cryptographic Weaknesses with Claude
#117Earlier quoted context omitted.
So $1-10k in Chinese model time, thus why we must ban them.
If a Chinese model can do it for $1-10K, then why hasn't one? Why have all the mathematical (and now cryptographic) breakthroughs come from OpenAI and Anthropic? Is it possibly because the Chinese models are so benchmaxxed they can't make novel discoveries?
Absence of evidence is not an evidence for absence of something.
Re: Discovering Cryptographic Weaknesses with Claude
#118I can already picture the faces of national security directors everywhere. "The attacks described in these two papers are the strongest attacks we have found to date. We are sharing them after a period of consultation with US government and industry leaders. But as we develop increasingly powerful cryptanalytic results, it would be prudent to consider how researchers should react if a language model were to discover…
Re: Discovering Cryptographic Weaknesses with Claude
#119I find that some of my friends and acquaintances have gotten obsessed with prompting style, "prompt engineering", which skills to use, which skills to build, "context engineering", and a billion other variations on "how to write smart things so the model does good". Friends, look at the prompts that Anthropic's own people are putting into the machine: > A few hours after the first message, we found that Claude was st…
Re: Discovering Cryptographic Weaknesses with Claude
#120I find that some of my friends and acquaintances have gotten obsessed with prompting style, "prompt engineering", which skills to use, which skills to build, "context engineering", and a billion other variations on "how to write smart things so the model does good". Friends, look at the prompts that Anthropic's own people are putting into the machine: > A few hours after the first message, we found that Claude was st…
Yeah, in fact you can actually make the model perform worst. You should allow the model to "think for itself" instead of pushing your reasoning into the prompt. You should give it simple prompt and steer it along the way. Skills, CLAUDE.md/AGENTS.md should only ever be used if the model struggle at something or doesn't know how to use something. Vast majority of project should never need a skill or CLAUDE.md. If you…