Paul HittandClaude Opus 5.5
b94480cfc3
"Game" sits in the attach row of a one-to-one chat only: pick chess, checkers, reversi or tic-tac-toe, and who goes first. The card shows the board from the engine's own board, row 0 at the top for the first player and turned round for the second, with whose move it is. Tap a piece and its targets are marked; tap one to send the move. A checkers jump is entered square by square, the path marked as it goes, and sent as one move once complete; a chess promotion asks for the piece; reversi marks its legal squares and offers a lone Pass when that is the only move; tic-tac-toe takes the tapped cell. Whatever is sent is exactly a move the engine offered. Under the board: decline or cancel before play starts, resign after a confirmation, offer a draw once it is the other person's move, accept or decline theirs, in one row; the result in words once it is over; "Your boards disagree" with "Start a new game" (same game, same sides) when out of step; and the moves, folded away. Plain colours that read in both themes, and every square labelled with its name and what stands on it. A move or an ending that did not reach them says so and changes nothing. The attach row now scrolls sideways instead of squeezing five buttons. Co-Authored-By: Claude Opus 5.5 <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.