From 5ae5a6d0553e34afc3cf19e96043f7e0e2b349ef Mon Sep 17 00:00:00 2001 From: Asai Toshiya Date: Fri, 24 Nov 2023 02:44:12 +0900 Subject: Remove "NIP-33" (#896) --- 89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '89.md') diff --git a/89.md b/89.md index be3d075..097bdcb 100644 --- a/89.md +++ b/89.md @@ -65,7 +65,7 @@ The third value of the tag SHOULD be the platform where this recommendation migh * `content` is an optional `metadata`-like stringified JSON object, as described in NIP-01. This content is useful when the pubkey creating the `kind:31990` is not an application. If `content` is empty, the `kind:0` of the pubkey should be used to display application information (e.g. name, picture, web, LUD16, etc.) * `k` tags' value is the event kind that is supported by this `kind:31990`. -Using a `k` tag(s) (instead of having the kind onf the NIP-33 `d` tag) provides: +Using a `k` tag(s) (instead of having the kind of the `d` tag) provides: * Multiple `k` tags can exist in the same event if the application supports more than one event kind and their handler URLs are the same. * The same pubkey can have multiple events with different apps that handle the same event kind. * `bech32` in a URL MUST be replaced by clients with the NIP-19-encoded entity that should be loaded by the application. -- cgit v1.2.3