Can we expect similar issues such as spectre and meltdown that intel experienced with speculative execution.. but, in the form of prompt injection/poisoning?
No, spectre is based upon speculative execution of code generated by another party. The breach is from the protection stopping that code from doing anything bad. Speculatve execution making things faster by varying amounts is used to turn those differences in timing into a signal.
You could possibly in-pronciple detect what a model with a censorship filter was actually saying, but not really. The signal is weak and needs lots of samples to get anything worth having. You just don't have that level of control to set things up.
Ok, I'll bite: no, considering these are very different domains and you don't get system access by getting the wrong speculative branch for your next text token, you just get a slightly different (but probably still related enough) text.
"In biology, we’ve established an access program, developed in partnership with the US government, to enable access to Claude Mythos 5.1’s advanced biology capabilities"
Having lived through Covid, this doesn't sound so good to me.
I do. I love to build things, though these things are not that meaningful yet as I want them to be. Most of these (except last 3 and that 'A calculator CLI...') are being actively used by many.
But I should not have shared a single `show hn` more than once.. that I will take care of going ahead.
One small thing: "Show new" seems to be missing.
reply