OverviewFilesCommitsIssuesDocsReleasesPeers

favela-peer commits / 1f6d560

README: four stale numbers, the bridge verbs, and a fleet claim I could not verify
Re-measured rather than adjusted: version 0.0.53 -> 0.0.58 tests 362 -> 395 asserts 865 -> 938 test files 44 -> 50 runtime ~36 s -> ~43 s rpc methods 98 -> 106 (case labels in dispatch's switch) The Status line claimed the daemon runs "on tabertron, ashatron and stortron". Verified two: 0.0.57 installed and running on tabertron, and on stortron for 5d02h. ashatron does not resolve from this host, so that third name is dropped rather than carried — and the line now dates its measurement, because a host list is the part of a README that rots fastest. Upstream holepunch READMEs have no Status section at all, which is the reason this one keeps only what `npm test` reproduces. Added a Bridges section. lib/bridge.js and five bridge-* RPC verbs existed with no mention in the file, and they are how this identity reaches a network the daemon is forbidden to know about. Stated that they are driven from favela-surface's routes rather than the CLI, which is why the CLI tables correctly do not list them. Also stated: buildCollect is exported and tested and has NO RPC verb, so nothing on this side can send one. buildClaim has a caller at rpc.js:404 and buildCollect has only test/bridge-collect.test.js. That is the peer half of what hyper-social #73 §3 called unexercised, and a reader comparing the four builders would otherwise assume all four are reachable. set-profile gained --banner on the CLI and the table had not. Glyph count 1 -> 0; the Boundary section's leading marker predates the style pass and the sentence says the same thing without it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1f6d56086be5009d4961d322e4032f04586d8bcf
by plankatron <fleeky@gmail.com> · 2026-09-20T20:41:23.000Z

Changed files (1) +28 -5

README.md +28 -5
……@@ -68,7 +68,7 @@ Refuses to start if another daemon already holds the socket.
6868| | |
6969|---|---|
7070| `profile` | display name and picture |
71| `set-profile [--name X] [--bio "…"] [--avatar <file>]` | `--bio ""` removes |
71| `set-profile [--name X] [--bio "…"] [--avatar <file>] [--banner <file>]` | `--bio ""` removes |
7272| `invite [--ttl <ms>]` | one-time invite for a browser |
7373| `browsers` | browsers you have admitted |
7474| `revoke <publicKey>` | retire a browser |
……@@ -94,7 +94,8 @@ Refuses to start if another daemon already holds the socket.
9494| `dismiss <feedKey>` | |
9595| `directory` | listings across registries you hold |
9696
97`lib/rpc.js` answers 98 methods; the CLI covers the ones a human drives.
97`lib/rpc.js` answers 106 methods; the CLI covers the 34 a human drives. The rest are what
98`favela-surface` calls — onboarding, rooms, namespaces, reach, and the bridge verbs below.
9899
99100## Primitives
100101
……@@ -128,15 +129,37 @@ Refuses to start if another daemon already holds the socket.
128129
129130## Boundary
130131
131⛔ No `atproto-*` or `ap-*` imports. No DAG-CBOR, no MST, no DID, no signed commit.
132No `atproto-*` or `ap-*` imports. No DAG-CBOR, no MST, no DID, no signed commit.
132133
133134`test/boundary.test.js` enforces this over every file in `lib/` and over the dependency list.
134135
136## Bridges
137
138A bridge carries this identity onto a network the daemon itself knows nothing about. The peer holds
139the client half; the ceremony and the signed bytes come from `favela-identity`, so the claimant and
140the verifier cannot disagree about them.
141
142| | |
143|---|---|
144| `bridge-policy` | what a bridge will accept |
145| `bridge-claim` | take a name on it |
146| `bridge-release` | give one up — permanent |
147| `bridge-front` | ask it to carry an identity this node holds |
148| `bridge-which` | which bridge carries a given name |
149
150Driven from `favela-surface`'s `/bridge/*` and `/did/*` routes, not from the CLI.
151
152`lib/bridge.js` also exports `buildCollect` — the request a node makes for what a bridge observed
153while it was unreachable. It is proven by `test/bridge-collect.test.js` and has **no RPC verb**, so
154nothing on this side can send one yet. The bridge half is built; see hyper-social #73 §3.
155
135156## Status
136157
137Working. 0.0.53, running on tabertron, ashatron and stortron.
158Working. `npm test` — 395 tests, 938 asserts, passing (`brittle-bare test/*.test.js`, 50 files,
159~43 s).
138160
139`npm test` — 362 tests, 865 asserts, passing (`brittle-bare test/*.test.js`, 44 files, ~36 s).
161Deployed as a pgh app. Measured 2026-09-20: 0.0.57 installed and running on tabertron and stortron,
162with this tree at 0.0.58.
140163
141164## License
142165