You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 84a7766
Browse filesBrowse the repository at this point in the historyBrowse files
8.**Every input modality is a first-class seam.** Keyboard, pointer, and
229
+
hotkey paths must not silently diverge: `Shift+Space` treated as plain
230
+
`Space` because the guard omitted `shiftKey` (PR #6862), keyboard
231
+
ownership not released on blur, modifier keys dropped on the non-mouse
232
+
path (PRs #5958, #6793, #6860, #6908, #7006). When adding an input
233
+
handler, enumerate the modalities that can reach it and test the
234
+
non-primary ones — that's where the defects were. (PRs #5958, #5972,
235
+
#6793, #6860, #6862, #6908, #7006)
236
+
237
+
---
238
+
154
239
## Key Patterns
155
240
156
241
**Nostr-first HTTP surface**: Buzz's primary API is NIP-29 over WebSocket. The relay also exposes a narrow HTTP surface: NIP-11/NIP-05 metadata, `POST /events`, `POST /query`, `POST /count`, workflow webhooks at `/hooks/{id}`, Blossom media, git smart HTTP, git policy hooks, and health probes. These HTTP paths all preserve the same host-derived community boundary.
Copy file name to clipboardExpand all lines: ARCHITECTURE.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -325,6 +325,15 @@ This prevents a race where a non-member receives live fan-out events from a priv
325
325
326
326
After registering, the REQ handler queries Postgres for stored events matching the filters (up to 500 per filter, hard cap). These are sent as `["EVENT", sub_id, event]` frames before `["EOSE", sub_id]`. New events arriving after EOSE are delivered via the fan-out path.
327
327
328
+
**Client consumption invariant.** A client rebuilding channel state must
329
+
open its live subscription before (or overlapping) the finite history
330
+
REQ — a gap between the last backfill page and live delivery silently
331
+
drops events and rebuilds stale state (PR #3995). When the relay sends a
332
+
terminal CLOSED, the subscription is removed server-side; any client-side
333
+
ownership tied to it (chunk/scope fences) must be released in the same
334
+
step, or live delivery stops permanently while the client believes it is
0 commit comments