From 6de35f9e6a50cd5bf88c0a350ef369919ac27f06 Mon Sep 17 00:00:00 2001 From: Jon Staab Date: Mon, 27 Nov 2023 06:22:15 -0800 Subject: [PATCH] Make client hints backwards compatible --- 89.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/89.md b/89.md index 097bdcbd..43d197fc 100644 --- a/89.md +++ b/89.md @@ -74,14 +74,14 @@ 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 -When publishing events, clients MAY include a `client` tag in the same format as the recommendation event's `a` tags. This has privacy implications for users, so clients SHOULD allow users to opt-out of using this 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. ```json { "kind": 1, "tags": [ - ["client", "31990:app1-pubkey:", "wss://relay1", "ios"] + ["client", "My Client", "31990:app1-pubkey:", "wss://relay1"] ] ... }