MeshBay — read-only public mirror https://git.meshbay.org/meshbay.git/atom?h=0.21 2026-10-17T21:15:02Z 2026-10-17T21:15:02Z Christophe Besson cbesson@gmail.com 2026-10-17T21:15:02Z urn:sha1:9462ac3067ce68ad90a3527b2144b86bd87bf89e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-15T15:45:41Z Christophe Besson cbesson@gmail.com 2026-10-15T15:43:15Z urn:sha1:63aa0ddd8c0ec49fe8b52b6b486b079887ed3112 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-07T20:43:00Z Christophe Besson cbesson@gmail.com 2026-10-07T20:43:00Z urn:sha1:4c8e4fb8b8fcd3f78bf4e3e736a058c351aac973 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-05T08:36:18Z Christophe Besson cbesson@gmail.com 2026-10-05T08:36:18Z urn:sha1:b8671635cd891068afee81fde05bed880124ec85 docs/MESHBAY_HTTP_API.md lists every route of the hub (by domain, with the authentication each requires) and of the node's loopback control API. It is written by docs/generate_http_api.py from the routes and their docstrings; test_http_api_doc.py fails when the file drifts from the code or when a route has no docstring, so a new route must say what it does. 79 routes had no docstring and get a one-line description; a few whose first line did not describe the route get a summary line. The login page's developer docs gain an API link next to Design and Protocol, in every language. README, MESHBAY_DESIGN.md (§0.1, §6.7, §7) and CLAUDE.md point to the listing; README also points to examples/. The examples scripts with a shebang become executable. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-03T13:06:44Z Christophe Besson cbesson@gmail.com 2026-10-03T13:06:44Z urn:sha1:01c4db74f3f234373a3e97da9cdc1bd8458a9f8b Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-09-30T13:16:25Z Christophe Besson cbesson@gmail.com 2026-09-30T13:16:25Z urn:sha1:8d96cf2314b45e0737f932998b5422c27a2ae72e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-09-25T15:43:28Z Christophe Besson cbesson@gmail.com 2026-09-25T15:43:28Z urn:sha1:3f3c67a4aff7b800c271e88e2bc5e5294b010fb9 The node-audience token (previous commit) is a change to what a peer must present, so it is a MAJOR per the versioning rule (§5.6): a pre-4.0 client presents its hub session token and a 4.0 node refuses it, and there is no compatibility branch, because leaving one would keep a hub credential reachable by every node (C6's lesson). So the floor moves with the version. - MNP_VERSION 3.4 -> 4.0 and MNP_MIN_SUPPORTED 3.0 -> 4.0 (meshbay_common); transport.js MNP_V/MNP_V_MIN -> 4.0 to match. - MIN_CLIENT_VERSION 0.13.0 -> 0.16.0 so a stale desktop client is told to update before connecting rather than meeting a handshake refusal it cannot read; the browser reloads this build from the hub. - Regenerate tests/golden/dispatch.json: the only change is the `v` the node stamps on outbound messages, 3.4 -> 4.0 (56 cases, v field only). - Document the split and the flag day: MESHBAY_DESIGN.md §5.2 (the handshake token is the MNP-audience token), §5.6 (the 4.0 flag day), register E10 and decision 23; MESHBAY_NODE_PROTOCOL.md §6.3 (authorize_token binds MNP_AUD) and the wire-version banner. Deploy is coordinated and atomic (common+hub+node+SPA together); a live browser-to-node validation and the deploy itself remain. common (173), node (1489, the pre-existing test_cli_golden argparse/prog artifact aside) and hub (1471) suites all green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-09-19T12:24:13Z Christophe Besson cbesson@gmail.com 2026-09-19T12:24:13Z urn:sha1:86188385cbdae1ee90c1dca7a7b9db2edef1ecd4 `ruff check .` had gone unrun long enough to report 568 errors, which is the same as having no linter: the next real finding would have been invisible in the noise. This is the 521 it fixes by itself, in 173 files, and nothing else — the 98 it cannot fix are the next commit. What actually changed: import sorting (225), imports nobody used (87, none of them a re-export — no `__init__.py` is touched, which was the one way this could have broken an import elsewhere), `datetime.timezone.utc` to `datetime.UTC` (69) and `asyncio.TimeoutError` to `TimeoutError` (18), both plain aliases on the 3.12 this project requires, `Optional[X]` to `X | None` (24), and f-strings with nothing to interpolate (19). Checked rather than assumed: every module in the three packages still imports, and the suite is 2893 passed — the same count, test for test, as the merge before it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2026-09-15T00:21:01Z Christophe Besson cbesson@gmail.com 2026-09-15T00:16:39Z urn:sha1:73ad8e4eb566fe682107fa7e50ef624591199e99 Browser idle sign-out (media playback counts as activity; not the desktop app), refresh idle window and maximum session length, in hours. Sign-out now revokes on the hub, and the profile has "sign out everywhere". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XuNrwLf5EFWCMHzfoEvnpm