Skip to content

NIP-22: Format should follow scope #1797

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

Open
vitorpamplona wants to merge 3 commits into
base: master
Choose a base branch
from
Open

NIP-22: Format should follow scope #1797

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cd3573b
Applies the formatting rules to the comments.
vitorpamplona Feb 20, 2025
c07c7e3
better wording
vitorpamplona Feb 20, 2025
056c596
uppercase key words
vitorpamplona Feb 20, 2025
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
4 changes: 3 additions & 1 deletion 22.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,9 @@ Comment

A comment is a threading note always scoped to a root event or an [`I`-tag](73.md).

It uses `kind:1111` with plaintext `.content` (no HTML, Markdown, or other formatting).
It uses `kind:1111` with the comment on `.content`.

Content formatting MUST follow the rules specified in the scope. If no rules are specified, it SHOULD follow kind 1 rules (no HTML, Markdown, or other formatting).

Comments MUST point to the root scope using uppercase tag names (e.g. `K`, `E`, `A` or `I`)
and MUST point to the parent item with lowercase ones (e.g. `k`, `e`, `a` or `i`).
Expand Down