Skip to content

docs(vision): add /buzz/v1 read endpoints to the protocol contract #7879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
baxen merged 3 commits into from
Sep 25, 2026
Merged

docs(vision): add /buzz/v1 read endpoints to the protocol contract #7879

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
07be13a
docs(vision): add /buzz/v1 read endpoints to the protocol contract
baxen Sep 24, 2026
69b8ffe
docs(vision): frame the protocol line as conversation-in-Nostr plus a…
baxen Sep 25, 2026
f8a0487
docs(vision): drop NIP-RS parenthetical
baxen Sep 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions VISION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,8 @@ Buzz extends the standard Nostr event format with custom kind numbers for enterp

New message type? New kind integer. Zero breaking changes.

**The conversation is Nostr; Buzz adds accessories around it.** Messages, threads, reactions, and the rest of the conversation are signed Nostr events, and Nostr reads must cover all of that state, so a standards-leaning Buzz client stays possible. Around it, the relay serves accessories that don't fit that shape: Blossom media, git smart HTTP, workflow webhooks, derived unread counts, and namespaced `/buzz/v1/...` endpoints for backend-for-frontend reads (thread catch-up, sync) over the same authoritative store. We start with this rule and refine it as more cases show up.

---

## Architecture
Expand Down
Loading