I don't speak for my former employers. Whatever I say about them or their products and services is exactly what I would say as a customer or industry observer.
Verifying my account on nostr
My Public Key: "npub15hq2p29dp2vsp83h2cah0cpj0ggmqp89v70e2xhfwjhkn0jftazqt84rum"
Find others at https://t.co/oc1rXiTFyp @nostrdirectory#nostr
@ArmandDoma Not all religions are theistic and not all support for honoring or respecting the "sacred" nature of some sites or artifacts is religious nor theistic.
Political posturing abhors nuance.
Great.
After your conviction, you can be the prosecution's star witness in Trump's historic third impeachment … and hopefully in the first ever trial of a former U.S. Commander-in-Chief before the @IntlCrimCourt at the Hague!
(Okay, maybe just co-defendant in the latter case)
Tautologically: your impeachments won't change that record …
… because you committed crimes!
You were NOT carrying out lawful orders when you ordered the extrajudicial murders of fishermen nor when your oversight of command executed "double-tap" strikes on civilian targets!
Hegseth: In the 250 years of our American republic, no Secretary of Defense has ever been impeached for carrying out lawful military operations. And in our case, successful ones.
@heynavtoor@pushmeet@GoogleDeepMind Better to prioritize drilling DOWN the stack, through system libraries, kernels, device drivers, down into firmware and microcode to the gate level logic.
Then automate re-use of the components as the foundational layers for every app.
@Vicnent@pushmeet@GoogleDeepMind I presume that these are limitations that apply to all software running on any system that has not separately achieved full formal verification.
The advancement to the state-of-the-art should be applauded nonetheless.
Just a few years ago, this achievement was not feasible.
Announcing a major milestone achieved by my team @GoogleDeepMind: we have proven key security properties of the machine code underlying the Signal messaging protocol. This is the first time the actual production code of a widely deployed protocol has been formally verified – by any method, with or without AI – and at this depth.
More than a research breakthrough, it’s a prime example of how frontier AI can be a force multiplier to counter the speed and scale of modern cyber threats.
Formal verification offers a higher standard of security; however, it’s extremely complex and time consuming, which is why in many cases it’s considered to be impractical. Similar efforts could take teams decades of combined effort. We did it in a month’s time.
Using AlphaProof Code, Google DeepMind's new agentic framework for formal verification that runs on LLMs including Gemini Carbon, we verified the Signal protocol down to the actual code running on devices. This milestone lays the groundwork for a future in which vital systems, from medical device firmware to power grid software, ship with mathematical proof that their protections work.
Reaching that future will take continued research from our community. In that spirit, we're open-sourcing our formal specifications and verification artifacts so others can build on this work.
On a personal note, this moment is of deep significance to me. I started my own research journey more than two decades ago as an intern working on checking the consistency of complex software systems. Seeing this grand challenge made practical with modern AI is extraordinary.
I'm extremely proud of my team members: Swarat Chaudhuri, Andrew Ferraiuolo, Anton Kovsharov, Tej Chajed, Sam Schlesinger, Karn Seth, Jonathan Katz, and Charles Sutton for taking on this grand challenge and delivering, and grateful to the Signal team for their partnership.
https://t.co/kN1eRYQ8fF
@Arvolear Yes they/we do.
Sometimes the demands of management and market force us to accept risk/exposure over more immediate failure (such as unemployment).
@billbrown@ejc3@HeapSmasher It «could» be more like that, if @Apple chose to create and maintain a Linux syscall compatibility layer.
But I think it would be a waste of their resources and a chronic maintenance and compatibility nightmare.
@ejc3@HeapSmasher Generally the folks who fail to understand the distinction between Docker running natively vs under MacOS are unaware of the distinctions between system calls and libraries functions, much less the nuances among different kernels and libc implementations.
@HeapSmasher@lsreq If you want more secure isolation, don't use containers (natively nor under HyperKit).
And for security, be seriously skeptical of the isolation you achieve through VMs!
@HeapSmasher@Docker@Apple@linuxfoundation Since @Grok payblocked my followup prompt, I decided to feed it to @AskPerplexity (which I am willing to pay for):
https://t.co/0jx3SkIf7s
tl;dr: Docker/MacOS requires more static resource allocation to the HyperKit Linux VM than Docker natively hosted under Linux:
@AskPerplexity I think the key takeaway is that agentic systems, in for in-house operations, can behave like web-scale (@slashdot-style) viral masses and ops must adapt to that.
Spectre sounds like an ambitious in-house software development project.
The issues described in that @AskPerplexity Discover article seem to be re-learning of web-scale capacity management (where any component might overwhelm adjacent service/resources capacities).