From b39e73cbb279ab0274e8cd0b84304a602fe1d5ef Mon Sep 17 00:00:00 2001 From: Christophe Besson Date: Sat, 10 Oct 2026 17:09:12 +0200 Subject: fix(android): what the first backup on a phone showed Slices are asked for in the address, not a Range header the WebView drops; a settings change runs at once; the notification is updated once a second; the SMS section says how to lift Android's restricted setting; the photo section says whether videos are included. Co-Authored-By: Claude Opus 5.5 --- docs/MESHBAY_DESIGN.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md index 5412d16..8d14e37 100644 --- a/docs/MESHBAY_DESIGN.md +++ b/docs/MESHBAY_DESIGN.md @@ -3430,9 +3430,10 @@ photos, in the same `YYYY/YYYY-MM` folders, under the same ledger, rules and unmetered network. `READ_MEDIA_VIDEO` is asked for when they are ticked in. The confirmation states the videos' count and size apart, because they are most of it. A file is never whole in the page: the upload reads it a chunk at -a time and each chunk is a ranged request to the phone (`Range: bytes=a-b`, -answered 206 by `ByteRange.kt`), so a video of gigabytes costs the WebView one -chunk of memory; the SHA-256 the ledger keeps is then read from the phone once +a time and each chunk is a ranged request to the phone (`?range=a-b` in the +address, served by `ByteRange.kt`; not a `Range` header, which the WebView +does not hand to the application that answers, found on a Pixel 9), so a +video of gigabytes costs the WebView one chunk of memory; the SHA-256 the ledger keeps is then read from the phone once the node has the file. The Photos tab shows them in their albums (ยง9.9). **A manifest, for a restore or a merge later.** The node keeps the files; only -- cgit v1.2.3