oak

A bit surprised that it’s written in rust, rather than Go. I suppose rust can take advantage of more low level apis, plus no overhead of garbage collection. edit: love that the community is not silo’d into a proprietary chat platform as well: > We welcome contributors! To join our community, we recommend joining the mailing list. - https://github.com/project-oak/oak?tab=readme-ov-file#gettin... I really wish more open source projects used mailing lists. 1) decentralized means of communication 2) able to join these communities from any type of environment (ie, corporate hell hole) without much friction. With discord, slack (especially at fortune 500s). It usually involved a whole process of approvals to get the damn thing installed and punch a hole through the firewall to get access to the service. No, using a personal email and device for

The lede is a little buried in that README [1]: ## Sealed Computing A canonical use of Oak is to build privacy-preserving sealed computing applications. In a sealed computing application, a node (usually a client device) sends data to an enclave application (usually a server), which processes data without the service provider hosting the enclave application being able to see the inputs, outputs, or side effects of the computation. [1]: https://github.com/project-oak/oak?tab=readme-ov-file#sealed... --- Seems like an attempt at a privacy-preserving alternative to running your whole phone OS image on a server?

You can actually look at what wasm is currently being used for beyond its connection to the JS ecosystem. It's a really exciting space. For example, there's a project called Oak (https://github.com/project-oak/oak) that basically allows your private information to be processed by servers without revealing them to the servers. It uses a bunch of technologies and wasm is a center piece for allowing a safe form of code execution. For another example, check out Mozilla's post about securing Firefox with wasm (https://hacks.mozilla.org/2020/02/securing-firefox-with-weba...). Again, here we compile C/C++ code with unknown memory safety properties into wasm and then compile that to native code. The benefit of doing it over directly compiling C/C++ to native code is that any memory safety issue is strictly sandboxed to be within the wasm module.

More interesting, is that from his blog I ended up on Project Oak, being written in Rust https://github.com/project-oak/oak