mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-22 16:35:52 -05:00
Add client tag to nip 89
This commit is contained in:
parent
b6c7a25510
commit
7f27800e27
13
89.md
13
89.md
|
@ -74,6 +74,19 @@ 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
|
||||||
|
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.
|
||||||
|
|
||||||
|
```json
|
||||||
|
{
|
||||||
|
"kind": 1,
|
||||||
|
"tags": [
|
||||||
|
["client", "31990:app1-pubkey:<d-identifier>", "wss://relay1", "ios"]
|
||||||
|
]
|
||||||
|
...
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
# User flow
|
# User flow
|
||||||
A user A who uses a non-`kind:1`-centric nostr app could choose to announce/recommend a certain kind-handler application.
|
A user A who uses a non-`kind:1`-centric nostr app could choose to announce/recommend a certain kind-handler application.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user