From 556eaa133e9cfe7f4c8e542708119fdfd311357e Mon Sep 17 00:00:00 2001 From: Doan Luu Duc Tai Date: Fri, 30 Oct 2026 21:39:57 -0500 Subject: Implement experimental file-based encrypted private chat Add fixed-suite Rust/WASI identity files, signed challenge authentication, ciphertext-only SQLite storage, a minimal LibreJS-compatible interface, and consistent backup snapshots. Keep production unchanged and document the local workflow, limits, source distribution, and browser recovery tests. --- README.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'README.txt') diff --git a/README.txt b/README.txt index 70a5931..5613a05 100644 --- a/README.txt +++ b/README.txt @@ -72,3 +72,16 @@ CHECKS AND LICENSES Detailed manual backup, recovery, deployment, and host setup instructions are in docs/OPERATIONS.txt. Read docs/POLICY.txt before changing conventions. + +EXPERIMENTAL CHAT BRANCH + + feature/private-chat contains a local Rust/WASI chat application. Start with + docs/CHAT-APPLICATION.txt for setup, protected files, tests, backup/restore, + source licensing, and security limitations. cargo stack chat --init appends + chat configuration to the existing single root .env; cargo stack chat runs + the local service. This does not deploy or enable production chat. + + SQLite snapshots now use the bundled SQLite C library. Portable stack + release builds consequently also require a musl C compiler on the development + machine, in addition to the Rust musl target. Runtime binaries remain static; + no new compiler is required on the VPS. -- cgit v1.2.3