two weeks, all Rust, no Python
two weeks ago we stopped shipping new solstone features so the journal’s core could finish moving off Python. that is done. the Python is gone.
not “mostly gone,” and not “behind a flag.” there is no Python left under the journal’s product tree at all. the last of it was deleted yesterday.
(new here? solstone is open source. your journal is the memory of your days: it lives on a computer you choose, and it stays there.)
the rustification
every line of Rust and Python in the journal’s tree, one point per commit, 4 august through 17 august.
fourteen days, one repo:
- Python went from 692,090 lines to 25,980. 1,565 files down to 70 (some build scripts and misc utils).
- Rust went from 61,814 lines to 678,905. 132 files up to 1,873.
where we are now
- every command an owner can type, all forty-four, runs on the Rust core.
- the mac’s local model runtime is native, running the same model linux runs.
- retention got better, nothing gets deleted off your disk by policy alone.
- two of the three fixes we sent upstream to NVIDIA’s open-source attestation SDK are merged (#27, #29); the third is still open.
confidential processing
since august 1, confidential processing has been available to approved scouts. if your device doesn’t have enough compute available, it moves the thinking off your device onto hosted confidential hardware, using the same local model but run by sol pbc instead, with no third-party AI provider in the path.
it runs on confidential GPUs that sol pbc operates inside Microsoft Azure, where the hardware cryptographically enforces a boundary that keeps the cloud host excluded from what’s being processed. no content is retained, no human reviews it, ever, and nothing is used to train.
your journal cryptographically verifies the hardware before anything is sent. if it can’t verify, it doesn’t send.
the terms are published, and none of it is required. it’s just available when extra capacity is needed.
what’s ahead
our first rust-only release across the board. we’re doing test runs and working out kinks continuously until we get there.
once our rust journal is stable on linux and mac, we’ll have a new mac journal app with it packaged, and in short order a windows journal app with it packaged as well.
and we are very eager to explore bundling the journal as a mobile app, so that you can take an older iphone or android, plug it in at home, and turn it into an always-on, always-available home for your journal.
see you in two weeks!
sol pbc is a public benefit corporation. the promises about your data live in article 8 of our filed articles of incorporation, not in a policy we could quietly change: it can’t be amended without jer’s personal signature, and after him the language can only get stronger, never weaker. what that means.