diff options
| -rw-r--r-- | 89.md | 6 |
1 files changed, 3 insertions, 3 deletions
| @@ -74,14 +74,14 @@ Multiple tags might be registered by the app, following NIP-19 nomenclature as t | |||
| 74 | 74 | ||
| 75 | 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. | 75 | 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. |
| 76 | 76 | ||
| 77 | ## Client tag | 77 | # Client tag |
| 78 | 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. | 78 | 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. |
| 79 | 79 | ||
| 80 | ```json | 80 | ```json |
| 81 | { | 81 | { |
| 82 | "kind": 1, | 82 | "kind": 1, |
| 83 | "tags": [ | 83 | "tags": [ |
| 84 | ["client", "31990:app1-pubkey:<d-identifier>", "wss://relay1", "ios"] | 84 | ["client", "My Client", "31990:app1-pubkey:<d-identifier>", "wss://relay1"] |
| 85 | ] | 85 | ] |
| 86 | ... | 86 | ... |
| 87 | } | 87 | } |