An accuracy sweep of the public pages plus a tone pass — several places described the
product by what it lacks rather than where it is.
Corrected, all understating what ships:
/roadmap said "From Android 0.6", /metadata said "in version 0.6" — both predate 0.8.
Version numbers removed rather than bumped: they date the sentence and go stale again,
and the landing page already reads the live version from the manifest.
/comparison said the iPhone app "is with Apple". It is not in review — 0.4.0 was
rejected, 0.5.0–0.8.0 are built and waiting to be submitted. Now "built and being
prepared for the App Store".
That last claim was corrected once before, on 2026-08-29, for describing a submission
that had not happened — and it came back on 08-31. A claim about somebody else's review
process is the one to be most careful with, and it has now drifted twice.
Reframed as in progress rather than absent:
"An outside audit hasn't happened yet" → "is still ahead of us"
Audit row reads Planned rather than Not yet
The 0.7 notice led with two faults and how they were handled; it now leads with the fix
and keeps the part a reader needs — replace it, installing over the top keeps your account
Verified rather than assumed: the comparison rows claiming Android parity for
federation, multi-homing and automatic key verification all hold. Android's key-log check
IS automatic — the "off by default" comment in its source describes the state before enforceKeyLogIfServed.
An accuracy sweep of the public pages plus a tone pass — several places described the
product by what it lacks rather than where it is.
**Corrected, all understating what ships:**
- `/roadmap` said "From Android 0.6", `/metadata` said "in version 0.6" — both predate 0.8.
Version numbers removed rather than bumped: they date the sentence and go stale again,
and the landing page already reads the live version from the manifest.
- `/comparison` said the iPhone app "is with Apple". **It is not in review** — 0.4.0 was
rejected, 0.5.0–0.8.0 are built and waiting to be submitted. Now "built and being
prepared for the App Store".
That last claim was corrected once before, on 2026-08-29, for describing a submission
that had not happened — and it came back on 08-31. A claim about somebody else's review
process is the one to be most careful with, and it has now drifted twice.
**Reframed as in progress rather than absent:**
- "An outside audit hasn't happened yet" → "is still ahead of us"
- Audit row reads **Planned** rather than **Not yet**
- The 0.7 notice led with two faults and how they were handled; it now leads with the fix
and keeps the part a reader needs — replace it, installing over the top keeps your account
**Verified rather than assumed:** the comparison rows claiming Android parity for
federation, multi-homing and automatic key verification all hold. Android's key-log check
IS automatic — the "off by default" comment in its source describes the state before
`enforceKeyLogIfServed`.
Not deployed. Part of #45 and #46.
added 5 commits
<ul><li>5b263746...1a0a93fa - 4 commits from branch <code>main</code></li><li>aa58447a - Say what is true, and say it as progress</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/12/diffs?diff_id=2001126569&start_sha=5b26374629d99c82f7a2ab94dd9d410b73014074)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
An accuracy sweep of the public pages plus a tone pass — several places described the
product by what it lacks rather than where it is.
Corrected, all understating what ships:
/roadmapsaid "From Android 0.6",/metadatasaid "in version 0.6" — both predate 0.8.Version numbers removed rather than bumped: they date the sentence and go stale again,
and the landing page already reads the live version from the manifest.
/comparisonsaid the iPhone app "is with Apple". It is not in review — 0.4.0 wasrejected, 0.5.0–0.8.0 are built and waiting to be submitted. Now "built and being
prepared for the App Store".
That last claim was corrected once before, on 2026-08-29, for describing a submission
that had not happened — and it came back on 08-31. A claim about somebody else's review
process is the one to be most careful with, and it has now drifted twice.
Reframed as in progress rather than absent:
and keeps the part a reader needs — replace it, installing over the top keeps your account
Verified rather than assumed: the comparison rows claiming Android parity for
federation, multi-homing and automatic key verification all hold. Android's key-log check
IS automatic — the "off by default" comment in its source describes the state before
enforceKeyLogIfServed.Not deployed. Part of #45 and #46.
added 5 commits
mainaa58447a- Say what is true, and say it as progressCompare with previous version
mentioned in commit
90e3bb6893changed the description