NIP-89: Fix heading levels (#2032)

This commit is contained in:
Yoji Shidara 2025-08-20 01:11:47 +09:00 committed by GitHub
parent c222f71102
commit 38bc891e67
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions

4
89.md
View File

@ -47,7 +47,7 @@ Multiple `a` tags can appear on the same `kind:31989`.
The second value of the tag SHOULD be a relay hint. The second value of the tag SHOULD be a relay hint.
The third value of the tag SHOULD be the platform where this recommendation might apply. The third value of the tag SHOULD be the platform where this recommendation might apply.
## Handler information ### Handler information
```jsonc ```jsonc
{ {
"kind": 31990, "kind": 31990,
@ -76,7 +76,7 @@ Multiple tags might be registered by the app, following NIP-19 nomenclature as t
A tag without a second value in the array SHOULD be considered a generic handler for any NIP-19 entity that is not handled by a different tag. A tag without a second value in the array SHOULD be considered a generic handler for any NIP-19 entity that is not handled by a different tag.
# Client tag ## Client tag
When publishing events, clients MAY include a `client` tag. Identifying the client that published the note. This tag is a tuple of `name`, `address` identifying a handler event and, a relay `hint` for finding the handler event. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this tag. When publishing events, clients MAY include a `client` tag. Identifying the client that published the note. This tag is a tuple of `name`, `address` identifying a handler event and, a relay `hint` for finding the handler event. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this tag.
```jsonc ```jsonc