From 38bc891e671fab9603e5129b01158bda844271df Mon Sep 17 00:00:00 2001 From: Yoji Shidara Date: Wed, 20 Aug 2025 01:11:47 +0900 Subject: [PATCH] NIP-89: Fix heading levels (#2032) --- 89.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/89.md b/89.md index 24aa3c57..dff4ea1d 100644 --- a/89.md +++ b/89.md @@ -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 third value of the tag SHOULD be the platform where this recommendation might apply. -## Handler information +### Handler information ```jsonc { "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. -# 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. ```jsonc