nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 06:45:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 89.md with preferred feedback format

Browse Source
This commit is contained in:
Dustin Dannenhauer 2024-01-12 10:07:42 +00:00 committed by GitHub
parent 18133f9575
commit 79c9784309
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
89.md
View File

@ -58,7 +58,8 @@ The third value of the tag SHOULD be the platform where this recommendation migh
["web", "https://..../a/<bech32>", "nevent"],
["web", "https://..../p/<bech32>", "nprofile"],
["web", "https://..../e/<bech32>"],
["ios", ".../<bech32>"]
["ios", ".../<bech32>"],
["pff", "preferred feedback format"]
]
}
```
@ -69,6 +70,7 @@ 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.
* `pff` stands for preferred feedback format and is an optional tag that describes how the application would like to receive additional feedback from `kind:7` reactions. The format specified in `pff` is used to inform the `feedback` tag of the `kind:7` customer feedback event described in [NIP-90 - Data Vending Machine](https://github.com/nostr-protocol/nips/blob/master/90.md). Both `pff` and `feedback` values should be strings and no commitments to representation are made here; instead applications consuming these tags should work together to align themselves.
Multiple tags might be registered by the app, following NIP-19 nomenclature as the second value of the array.