Project update: 15 November 2026. GitHub pull request #12: merged into GitHub source, not necessarily deployed. Commonveil has not been independently security audited.
The Rust backend implemented conversations, encrypted messages, scheduled sends and Web Push notification handling.
Why this matters
Moving messages between servers must not require a server to inspect the message content. This stage covers the surrounding delivery mechanisms while retaining existing subscription formats. The push implementation follows established Web Push standards, and compatibility tests compare the Rust responses with the older backend.
Detailed change record
The public engineering notes below describe what was implemented or proposed and the evidence recorded with the change. Historical instructions in the notes describe the pull request at the time it was raised.
Stage B4 of moving the self-hosted server to Rust.
/api/functions/conversations,/api/functions/messages(with send-later and check-ins) and/api/functions/notificationsin Rust.- Web Push (
webpush.rs): RFC 8291 payload encryption (matches the RFC's worked example byte for byte) and VAPID signing. The site's push key is read and written in the same format as the Node.js server, so existing subscriptions keep working. tests/parity_messaging.rs: the same 128-request script against both servers, each on a fresh site, with real envelopes and signatures from Secure Net's Rust client code. Every status and answer matches once random values are blanked.- Not yet: server messages in
poll(answers 501NOT_YETuntil the servers stage), and delivering waiting messages when they fall due (the scheduled tasks stage). The Docker image is unchanged.
Decisions and principles behind the work
Comutability is building towards privacy, user control and genuinely self-hostable software. That does not mean every proposal is already deployed. The Rust backend is being checked for parity with Node.js before it can replace the existing Docker image.
What comes next
Verify notifications on actual browsers and devices before declaring the new backend production-ready.

