All blog posts
Updates 2 min read

Commonveil Rust Adds Encrypted Files, Events and Voice

A later Rust backend stage completed voice, encrypted events, file delivery, moderation and protocol-facing handlers.

By Comutability Published Update from
Encrypted communications illustration with a file, voice microphone and protected devices.

Project update: 15 November 2026. GitHub pull request #15: merged into GitHub source, not necessarily deployed. Commonveil has not been independently security audited.

A later Rust backend stage completed voice, encrypted events, file delivery, moderation and protocol-facing handlers.

Why this matters

The platform needs to work as a community space rather than a single-purpose messenger. Events, shared files, calls and moderator workflows create separate permission and encryption boundaries. This stage brought those backend functions together, including private file storage and short-lived links, without treating passing tests as independent certification.

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.

Ports the last backend functions to the Rust server, so none answers 501 any more.

  • voice: voice and call passes, with the per-minute limit.
  • events: events and answers, as encrypted items.
  • files: encrypted parts, private storage on disk (file_store), short-lived HMAC-signed links served at /api/files/*, and the clean-up the scheduled tasks will call.
  • moderation: reports encrypted to moderators, review, escalation, warnings with automatic steps, notes, pardons, purges and the policy.
  • protocol: actor documents, prekeys, bundles and the sealed-envelope mailbox.
  • snips: the proposals forum, including reading proposals from GitHub with ureq.
  • Unknown function names now get Node's 404 Unknown function.

Verified

  • tests/parity_more.rs: the same script runs against the Node.js and Rust servers on fresh sites with five people. Every status and answer matches once random values are blanked. Downloads through the signed links are byte-identical, and a bent link is refused by both.
  • Unit tests for the file store's links and for parsing a proposal's header.
  • cargo clippy --all-targets -D warnings and the full cargo test pass locally.

Not compared

  • Reading proposals from GitHub: the Node.js server can't be pointed at a test copy of GitHub, so only the "forum off" path is compared.

Outstanding

  • Realtime rooms (websockets), scheduled tasks, updates and federation, then the Docker switch.

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

Review file retention, rate limits, moderation handling and voice permissions in a realistic self-hosted environment.

Check the sources

Sources and further reading

Explore the evidence and original project records behind this article.