Paul HittandClaude Fable 5.1
4cfc044198
Two security operations discarded their result, the same two the iPhone had. One commit because both wires live in the view model. Block: the token revoke was a nested runCatching whose value nobody read. The block must not fail because the follow-up did, and that reasoning was right; making the follow-up silent was not. A revoke that fails leaves the blocked person holding capabilities that deliver sealed to this inbox, the opposite of what "Blocked" now says. Kept the block, surfaced the failure, and said that blocking again retries it. Sign-out: the device revoke was discarded on the line before the keys that authorise it are destroyed, so a failure was unrecoverable and invisible. What it leaves is a dead device row the relay fans every envelope to and every sender spends a prekey on; one was found this morning with 42 undelivered. The device id is now kept in preferences, not the vault, because the vault is destroyed a line later and a note there would not survive. Keyed by account, retried on the next sign-in to that account, cleared only when the relay accepts. The helper's tests round-trip the note, keep it account-scoped, and wipe filesDir, which is what destroy does to storage, to prove the note lives elsewhere. The view-model wiring is covered by compile and the suite; there is no view-model harness, so the two wires are verified by reading. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Flamenet Messenger. Android
The Android app, and the two libraries under it. The product's site is at https://flamenetmessenger.com.
engine/ the protocol: X3DH, Double Ratchet, sealed sender, safety numbers,
key transparency. Plain Kotlin/JVM — no Android in it at all.
client/ the relay transport: HTTP, auth, the §8 routes.
app/ the Compose app.
interop/ the cross-engine driver; not shipped.
engine and client are deliberately plain JVM libraries. The protocol has
nothing to do with Android, and keeping it off the platform means their tests
run anywhere a JVM does, no SDK, no emulator, no device, which is also what
lets them gate in CI on Linux:
./gradlew :engine:test :client:test
The app's own unit tests need the Android SDK but still no emulator (Robolectric):
./gradlew :app:testDebugUnitTest
Where it stands
PARITY.md is the definition of done for this app, read that, not this. Every row there names the iOS file it came from so it can be re-checked rather than trusted. Headlines: messaging, groups, attachments, voice notes, stories, calls, sealed sender, key transparency and the encrypted vault are built and tested, and a cross-platform round trip against iOS is verified.
If a claim here ever disagrees with PARITY.md or with the tree, believe those, and fix this.
Why the engine came first, and is held to the vectors
An Android client needs the protocol implemented a third time, and the third
implementation is the one that finds the places where the specification says
less than the two existing engines quietly agreed on, but only if it is
written against the spec and the published vectors rather than against a
reading of our own Swift and JavaScript. So the engine is held to
test/vectors/protocol-v1.json in
flamenet-e2e, the same file the
other two engines are checked against, read from that repository rather than
copied here, because a copied vector file drifts and a drifting vector file
stops being a check. PublishedVectorsTest looks for it beside this checkout
and fails loudly if it cannot find it; FLAMENET_VECTORS overrides the search.
Two implementations that agree may both be wrong in the same way, especially when one was written while reading the other. The audit-path ordering in §19 is the worked example: a top-down reading of a bottom-up path produces the correct root for every left-spine index, so it passes any test that only checks index 0. The vector file pins a right-descending index for that reason, and the Kotlin tests assert both that the published path verifies and that the same path reversed does not.
If this engine ever disagrees with the file, the interesting question is which of the three is wrong, not this one by default.
Contributing and security
- CONTRIBUTING.md, building (JDK 21,
JAVA_HOMEis not optional on a Mac), the test gate, and the platform traps that cost an hour each. - PARITY.md, what iOS does, what this does, and what is left. It is the definition of done for this app.
- SECURITY.md, threat model and where to send a vulnerability report. Not an issue tracker matter: security@flamenetmessenger.com.