nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Make client hints backwards compatible

Browse Source
This commit is contained in:
Jon Staab 2023-11-27 06:22:15 -08:00 committed by fiatjaf_
parent 1a106c6bff
commit 6de35f9e6a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
89.md
View File

@ -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. 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 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. 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 ```json
{ {
"kind": 1, "kind": 1,
"tags": [ "tags": [
["client", "31990:app1-pubkey:<d-identifier>", "wss://relay1", "ios"] ["client", "My Client", "31990:app1-pubkey:<d-identifier>", "wss://relay1"]
] ]
... ...
} }