MeshBay — read-only public mirror https://git.meshbay.org/meshbay.git/atom?h=0.20 2026-10-15T13:09:58Z 2026-10-15T13:09:58Z Christophe Besson cbesson@gmail.com 2026-10-15T13:09:58Z urn:sha1:39cac2878de059992cb09a1ccf09b6bcece99fae READ_SMS sits behind restricted settings outside a store and Play keeps it for the default SMS application: not worth a second build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-15T12:25:00Z Christophe Besson cbesson@gmail.com 2026-10-15T12:25:00Z urn:sha1:28c77b7648b2a44a18be64ec44344d91cccfd742 Ticking "also e-mail it to me" at registration sent the recovery key R in the register body, and the hub appended it to the verification e-mail: the hub saw R in clear on its way out, and the resend door — no captcha — let anyone who knew a pending username and address have the hub mail a "recovery key" of their choosing. The box is gone. The recovery screen offers "E-mail it to myself", a mailto: link that opens the person's own mail application with the key filled in; the desktop shell hands mailto: to the system (http, https and mailto only) and the Android shell to a mail application (ACTION_SENDTO). The CLI drops --email-recovery-key and prints the key, as before. The hub mails the code alone, and refuses a register that still carries a recovery_key rather than dropping it, so an older client offering the option cannot tell someone their key was sent when it was not. A mailbox holding R remains, with the reset code that reaches the same mailbox, enough to recover the account's identities; the link says so, and it is the person's choice. Checked in Chrome and Firefox (headless, the real page against a stubbed hub) and by the CLI's end-to-end registration against a local hub. The Android change was not built here, and the desktop link was not clicked in the application. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-14T11:34:47Z Christophe Besson cbesson@gmail.com 2026-10-14T11:34:47Z urn:sha1:51705056a578d2649a989bf14a056fbcfae58a6b Sign-up and passphrase reset sent every visitor's address and browser details to Google, which needed a consent the sign-up form could not ask for freely. The hub now issues its own challenge (ALTCHA's scheme, signed with a key derived from the hub's private key, single-use, 30 minutes) and the page solves it with SubtleCrypto while the form is filled in. - GET /v1/users/captcha issues a challenge; 404 captcha_disabled when off. - [captcha] enabled / max_number replace site_key / secret_key, which are now ignored with a warning; MESHBAY_CAPTCHA_ENABLED replaces the old variables. - No Google origin left in the CSP of the hub, the desktop shell or the Android shell; captcha_site_key leaves /v1/hub/info. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-11T22:17:32Z Christophe Besson cbesson@gmail.com 2026-10-11T22:17:32Z urn:sha1:14911aae21ec4975f7a805b91e3c4867cb41974b A whole-root walk now checks its root before every file: removed or ejected, it stops instead of reading the drive to the end; paused, it finishes from the hash cache alone. A paused root is not watched, not swept by reconcile and survives a restart (roster), its indexed files stay served. Resume runs the reconcile sweep over the root, so entries and their enrichment are kept. Signed root_pause / root_resume over MNP, loopback routes, CLI `root pause|resume`, a pause button on the indexing dock and pause/resume in the roots table of Group settings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-10T15:09:12Z Christophe Besson cbesson@gmail.com 2026-10-10T15:09:12Z urn:sha1:b39e73cbb279ab0274e8cd0b84304a602fe1d5ef 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 <noreply@anthropic.com> 2026-10-10T14:29:20Z Christophe Besson cbesson@gmail.com 2026-10-10T14:29:20Z urn:sha1:7957fa686eb6e8cf57bcb62ff4e6d2785693030b A WhatsApp section takes WhatsApp's folder through the picker, sends its encrypted Databases and Backups (not the dated copies of earlier weeks) into <folder>/<account>-whatsapp, and names the restore set in the manifest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-10T14:15:48Z Christophe Besson cbesson@gmail.com 2026-10-10T14:15:48Z urn:sha1:24547e4efd3a45b36b3bea8c29cfc687230a6d3a Photos, videos and files record, per file, their path on the node, their path and album on the phone, dates, size and SHA-256, uploaded as meshbay-manifest/manifest-<date>.jsonl once the run is done. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-10T13:50:39Z Christophe Besson cbesson@gmail.com 2026-10-10T13:50:39Z urn:sha1:1c97ffb91bb4928022e995709d7e55b19cfd18eb A Files section takes folders through the system picker (no storage permission), refuses DCIM, Pictures and Movies, skips what the photo backup sends, and runs on the photo backup's own runner into <folder>/<account>-drive. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-10T13:11:52Z Christophe Besson cbesson@gmail.com 2026-10-10T13:11:52Z urn:sha1:1fd7bbcd038cddf40540bae7083b9adf4c728912 A 'Videos too' option, off by default, sends them into the same YYYY/YYYY-MM folders. Files are read from the phone a ranged chunk at a time, so a large video is never whole in the page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-10T12:52:57Z Christophe Besson cbesson@gmail.com 2026-10-10T12:52:57Z urn:sha1:3bad2b50187f55463588a2d4e74fa9df4beb35b8 A Calendar section sends every calendar the person can edit, as a dated .ics, into <folder>/<account>-calendar once a day when it changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>