Paul HittandClaude Opus 5.5
78ea0ae11b
DESIGN 1b and 3 in the app, in one-to-one chats and groups. Cards: the attach panel offers a card with one of the nine flamenet.io fronts (shipped as assets/cards, titles drawn as text), to, message, from, and an optional day it stays sealed until, at most 400 days ahead. The receiver sees the front and "Opens on <date>" until then, and the card opens by itself when the day comes; the sender's copy is open and says whom it is sealed for. Copy, report and forward never hand over a card still sealed here, and a forward goes out unsealed. Events: title, a time or all day, an optional end, place and note. The card shows when it is in the reader's zone, the organizer's time when their clock reads differently, who answered what, Going / Maybe / Can't go in one row with "Everyone in this chat sees your answer.", and Add to calendar through the system's own insert sheet. Only the organizer is offered Change event and Cancel event. Revisions go out under a fresh mid and fold into the card the event first arrived on. Arrivals: answers fold onto their event and only redraw it, never marking a chat unread or notifying; one that comes before its event is held in memory until the event lands. A card or event from this account's own other device is kept only when it names a group. With previews on, a card or an event that arrives alone is announced as DESIGN words it, and never with a card's words. Nothing new is written for an off-the-record chat: every change goes through record and mutateHistory. Rows carry card, ev, org and rsvp, and HistoryRowsCarryEveryFieldTest reads record() and Session.Line from source and fails until a new field is carried by the backup, listed in BackupPayload.NOT_CARRIED, and read back. 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.