Skip to content
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

Clearly informs that kind 1 replies can only be used with kind 1 events. #1690

Merged
merged 1 commit into from
Feb 7, 2025
+3 −2
Merged

Clearly informs that kind 1 replies can only be used with kind 1 events. #1690

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 3 additions & 2 deletions 10.md
View file
Original file line number Diff line number Diff line change
@@ -10,15 +10,16 @@ This NIP defines `kind:1` as a simple plaintext note.

## Abstract

This NIP describes how to use "e" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event.

The `.content` property contains some human-readable text.

`e` and `p` tags can be used to define note threads, replies and mentions.

Markup languages such as markdown and HTML SHOULD NOT be used.

## Marked "e" tags (PREFERRED)

Kind 1 events with `e` tags are replies to other kind 1 events. Kind 1 replies MUST NOT be used to reply to other kinds, use [NIP-22](22.md) instead.

`["e", <event-id>, <relay-url>, <marker>, <pubkey>]`

Where: