We are sad to inform our community that Marina Zhurakhinskaya died on Saturday. Outreachy wouldn't exist without her dedication, which continued until her last day. sfconservancy.org/news/2022/ju

Congratulations to the 66 interns selected for this Outreachy round, as well as all of the applicants who completed the application process!


Check out our new explainer video narrated by our own ED @o0karen0o
created by Chris Rogers.
We're so happy to be able to share our vision of software freedom with you in this new video!

RT @JNRaeside
#DoctorWho - Ncuti Gatwa. You’re welcome.

The most promising of these IMO is Crystal. Its syntax is inspired by Ruby, but it's statically typed and ahead-of-time compiled with LLVM. Unlike Go, it has sum types which are used to represent nil-able values, like Rust's Option<T>. Like Go, it has a garbage collector, and uses green threads and channels for concurrency.

Show thread

I suppose it has a lot to do with my preference for working in openly collaborative communities and non-profit organizations. While that trend started for software in the '70s (don't forget BSD) and '80s, and is now so common we can't imagine a world without it, historically there hasn't been a lot of that in hardware. But that's changing, and open hardware today is every bit as exciting as in the '00s.

It isn't even really a change of interests for me, I had a soldering iron in my hands at the age of 3, and was designing simple circuits before I was 10.

That doesn't mean I'm not working on anymore, in fact, the two interest areas are very deeply connected. We can't have secure and reliable software if the underlying hardware is violating confidentiality and correctness all over the place.

My PhD dissertation was three alternative approaches to eliminating entire classes of speculation-related vulnerabilities, both the currently known variants and future-proofing against future variants that haven't been discovered/reported yet.

My focus for the past few years has been microarchitecture security, specifically the speculative execution vulnerabilities (Spectre, Meltdown, etc). It started as PhD work at the University of Cambridge, but has grown beyond that, into a working group at riscv.org, and a fun new job.

I've never been a particularly active Twitter user, so the barrier to exit is minimal.


A personal micro-instance of Mastodon (μon)