Paul HittandClaude Opus 4.8
4d8fc5b09c
RelayAccounts was at 0% — every route a person meets before they can send a single message, sign-up through password reset, including the error mapping that decides what they are told when it goes wrong. The error mapping earns as much attention as the happy path. These are the only failures somebody sees before they have an account, and a 409 shown as "something went wrong" instead of "that name is taken" is the difference between fixing it in five seconds and giving up. So there are tests for the taken username keeping the relay's own words, a wrong password arriving as Unauthorized rather than a generic failure, 429 carrying the relay's Retry-After and still being throttling without one, a non-JSON error body surviving as readable text, and an unreachable relay being Transport rather than a rejected password. Two of my assertions were wrong and the code was right, which is worth recording. Unauthorized and Unavailable deliberately keep the relay's text in `body` and give `message` a fixed string, because the type is a decision rather than a diagnostic — Unauthorized triggers exactly one retry, and a caller matching on a string to decide that eventually matches wrong. For 451 the fixed sentence is a product decision too: the download site is not geo-gated, so somebody can read the page, install the app, choose a password, tap sign up and be shown "relay returned 451", which mentions nothing about their country and cannot be retried past. The test now pins that wording. Also pins the compatibility details: an email goes in the `username` field because that field has always meant "username or email" and a client that only sends usernames rejects half the people who typed what they were asked for; a self-hosted relay's 404 on the shared-session route is the correct answer rather than a misconfiguration; and the handle travels beside the token rather than inside it, so a relay cannot correlate its users with another product's. RelayAccounts 0% -> 100%, client 57.7% -> 63.2% lines. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Flamenet Messenger — Android
The Android app, and the two libraries under it.
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 as of 2026-08-28: messaging, groups, attachments, voice notes, stories, calls, sealed sender, key transparency and the encrypted vault are built and tested; a cross-platform round trip against iOS was verified on 2026-08-26.
⚠️ This file said "Nothing here is an app yet" until 2026-08-28, above a tree containing the finished app — the README described the repository as it was when the engine landed and nothing updated it as the app grew around it. 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.