diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-10-08 11:40:17 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-10-08 11:40:17 +0200 |
| commit | 2860f1de75af1d44d35292ecbf79c68f02409d19 (patch) | |
| tree | 01096649c0cf475403f31bff803a23a955ca3397 /docs/MESHBAY_DESIGN.md | |
| parent | c27e04c88557716bbe8e42b9174ba9b07f90facf (diff) | |
| download | meshbay-2860f1de75af1d44d35292ecbf79c68f02409d19.tar.gz | |
feat: sign Android releases with the release key
assembleRelease reads the key from ~/.gradle/gradle.properties and fails
without it instead of falling back to the debug key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'docs/MESHBAY_DESIGN.md')
| -rw-r--r-- | docs/MESHBAY_DESIGN.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md index 18b23cf..9c42c62 100644 --- a/docs/MESHBAY_DESIGN.md +++ b/docs/MESHBAY_DESIGN.md @@ -3444,9 +3444,11 @@ narrow bridge — and Android has all three: keeps the WebView reported visible and holds a media-playback foreground service; nowhere else, because a page never hidden is never throttled. -Release builds are signed with the development key until the release key exists -(Stage D12); §2.3's sentence about who holds a signing key applies to whichever -store distributes them. +Release builds are signed with the release key, distributed as a direct APK; +the key stays outside the repository and a release build without it fails +rather than falling back to the development key. §2.3's sentence about who +holds a signing key applies to whichever store distributes them, if one ever +does. ### 11.4 Casting @@ -4027,7 +4029,7 @@ process runs it — `systemctl --user` on Linux, Task Scheduler on Windows. | — | **Bitmap subtitles** (PGS, VOBSUB — about a fifth of the embedded streams). No WebVTT without OCR; they are not listed rather than listed and blank. Burn-in covers them and costs `-c:v copy`, which is what the eight-slot sizing assumes never happens | | — | Delegation (§3.4) | | — | Tier 3 roster attestation (§3.3) | -| — | **Android: phone behaviour and release** — the back button driving the page, recovery from a network handover, keeping a download alive with the screen off, lock-screen media controls, and a release key (§11.3) | +| — | **Android: phone behaviour and release** — the back button driving the page, recovery from a network handover, keeping a download alive with the screen off, lock-screen media controls, and an update channel (§11.3) | | — | **Federation between two hubs.** The protocol is written and switched off in the code (§7.6); what is not built is one run between two machines | ### 15.3 Open, and why each is where it is |