Skip to content

NAP-02: Chat direct message open topic - #22

Closed
dskvr wants to merge 1 commit into
masterfrom
nub-02-chat-open-dm
Closed

NAP-02: Chat direct message open topic#22
dskvr wants to merge 1 commit into
masterfrom
nub-02-chat-open-dm

Conversation

@dskvr

@dskvr dskvr commented May 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds NAP-02 for the chat:open-dm IFC topic.
  • Defines { pubkey, displayName? } as the direct-message navigation payload.

Why

  • Direct-message navigation needs explicit topic semantics independent of generic IFC transport.

Spec / API surface

  • Discovery: shell.supports("ifc", "NAP-02").
  • Manifest dependency remains ["requires", "ifc"].

Compatibility

  • Existing IFC implementations can continue using the same topic string and JSON payload.

Validation

  • git diff --cached --check passed before commit.
  • Checked for private implementation references in the spec and README row.

Non-goals

  • Encryption, relay selection, chat history retrieval, shell window policy, and generic IFC transport.

Follow-ups

  • Companion topic PRs cover profile and stream context semantics separately.

Supersedes the chat:open-dm portion of the closed umbrella topic payload PR #20.

@dskvr

dskvr commented May 25, 2026

Copy link
Copy Markdown
Contributor Author

Closing in favor of the namespace-family shape requested after review. The current replacement packet keeps profile:* in #21 and stream:* in #26; chat:open-dm is deferred rather than kept as a separate tiny numbered NUB in this round.

@dskvr dskvr closed this May 25, 2026
@dskvr dskvr changed the title NUB-02: Chat direct message open topic NAP-02: Chat direct message open topic Jun 3, 2026
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