Skip to content

feat(cli): expose exact channel visibility - #6353

Draft
loganj wants to merge 1 commit into
mainfrom
larry/cli-channel-visibility
Draft

feat(cli): expose exact channel visibility#6353
loganj wants to merge 1 commit into
mainfrom
larry/cli-channel-visibility

Conversation

@loganj

@loganj loganj commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

🤖 Larry authored this change.

Summary

  • Make buzz channels get --channel <uuid> report whether the exact channel is open or private while preserving its existing metadata fields.
  • Fail instead of returning an incomplete or misleading result when the channel metadata has missing, malformed, duplicate, or contradictory visibility markers.

Details

The command now translates the channel metadata event's single-element public marker to "visibility": "open" and its private marker to "visibility": "private".

Focused tests pin the complete normalized open output, preservation of existing fields for private output, and rejection of missing, malformed, and contradictory visibility metadata. This change is limited to the exact channel lookup; channel listing, relay authorization, Desktop, and downstream intake behavior are unchanged.

Origin: buzz://message?channel=e7347028-9313-4c0f-8690-9f55409fd063&id=4c6ef01e3d33b0ec87c690e899a95a8e608fa594630b7371919ba5b9d9b0bd96

Project NIP-29 channel visibility into exact channels get output and fail closed when the metadata marker is absent, malformed, or ambiguous.

Signed-off-by: loganj <loganj@squareup.com>

Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
@loganj
loganj force-pushed the larry/cli-channel-visibility branch from 7876ba4 to 55308a7 Compare August 19, 2026 22:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant