Skip to content

Releases

PR 226 Windows cache-commit regression

Choose a tag to compare

@itz4blitz itz4blitz released this 07 Nov 21:09
0b75773

Windows-only normal-app regression for TinyComms/tinyclient#226 at b7f02bda8869ee9c0c706ec416fb98475d51b583.

Both sides use release-profile normal app bundles and fresh invented fixtures. Base 7ffa840a9beb7a7eb8017c679bc4ea1d82710876 opens the encrypted message during an isolated cache-append failure, then loses it after repair/index rebuild/cold restart. Branch refuses the failed cache commit and restores the same message after repair/restart. Exact message IDs, scoped IPC, durable-cache presence and actual conversation pixels agree.

Both recordings were started before driver steps, captioned with commit/step labels, decoded, dimension/duration checked, and visually inspected. Base has only the expected history-loss assertion failure; branch has none. proof.json carries binary hashes and evidence scope. No aggregate e2e-proof, other-platform, power-loss, installed-user recovery or software release certification is claimed. This is an evidence archive, not a tinyclient software release.

tinyclient PR226 Linux history regression at 27cd072

Choose a tag to compare

@itz4blitz itz4blitz released this 08 Nov 05:37
0b75773

Linux-only normal-app matched history regression for TinyComms/tinyclient#226 at exact commit27cd07263a49176fcbca55f1538541ef8d26547c, against official base7ffa840a9beb7a7eb8017c679bc4ea1d82710876.

An isolated sealed-cache append failure lets the base display a message, then lose it after repair and cold restart. The fixed branch refuses the unsaved read, then recovers and durably caches the same message after storage repair/restart. Exact message ids, scoped IPC, cache-file presence and native conversation pixels agree. Invented people, fresh independent databases, stable wrapping keys before first launch; no key/group resets or ratchet rewinds.

Both recorders started before driver steps. Videos were captioned, decoded, dimension/duration checked and visually inspected. The branch was built directly from the pinned source archive with release features and explicit embedded commit; all archived source files were checked unchanged after build. This is Linux-only evidence, not aggregate e2e-proof, release certification, affected-install recovery or a power-loss guarantee. Earlier Windows proof remains scoped to its original b7f head. This is a test evidence archive, not a tinyclient software release.