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

Update 90.md with new feedback tag in customer feedback event

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

9
90.md
View File

@ -181,23 +181,26 @@ Any job feedback event MIGHT include results in the `.content` field, as describ
## Customer feedback
Customers can give feedback about a job result back to the service provider via a `kind:7` from [NIP-25 - Reactions](https://github.com/nostr-protocol/nips/blob/8331354947f2d577e13eb5da4a56133071cb1019/25.md) with `e` and `p` tags that specifically refers to the note from which the DVM responded (the final result from the DVM).
Customers can give feedback about a job result back to the service provider via a `kind:7` from [NIP-25 - Reactions](https://github.com/nostr-protocol/nips/blob/8331354947f2d577e13eb5da4a56133071cb1019/25.md) with an additional `feedback` tag along with `e` and `p` tags that specifically refers to the note from which the DVM responded (the final result from the DVM).
```json
{
"kind": 7,
"content": "<content>",
"tags": [
["feedback", "<custom feedback string for the DVM>"],
["e", "<the id of the note that the DVM responded with>"],
["p", "<the pubkey of the note that the DVM responded with>"],
["k", "< (optional) the kind of the note that the DVM responded with>"]
["k", "<the kind of the note that the DVM responded with>"]
],
"pubkey": "79c2cae114ea28a981e7559b4fe7854a473521a8d22a66bbab9fa248eb820ff6",
"created_at": 1682790000
}
```
* `content`: Feedback string to the service provider. Could be "liked", "disliked", a score between an arbitrary range, a text string such as "worked but took too long", etc. but should be in accordance with [NIP-25 - Reactions](https://github.com/nostr-protocol/nips/blob/8331354947f2d577e13eb5da4a56133071cb1019/25.md) The representation of the feedback should be up to the decision of the client that enables the user to interact with the service provider. DVMs may specify how they would like feedback when announcing themselves via [NIP-89 - Recommended Application Handlers](https://github.com/nostr-protocol/nips/blob/master/89.md).
* `content`: Feedback string to the service provider consistent with [NIP-25 - Reactions](https://github.com/nostr-protocol/nips/blob/8331354947f2d577e13eb5da4a56133071cb1019/25.md).
* `feedback`: Additional feedback that is outside the scope of [NIP-25 - Reactions](https://github.com/nostr-protocol/nips/blob/8331354947f2d577e13eb5da4a56133071cb1019/25.md). This could be a message from the user such as "worked but took too long", or a score in a custom range (i.e. a Likert scale score of 1-5 or 1-100). Best practice is to check if the NIP-89 of the DVM is asking for a preferred feedback format and request the user to enter feedback in that format. The preferred format of the DVM's feedback from the customer is stored in the `pff` tag of the NIP-89 event. DVMs may specify how they would like feedback when announcing themselves via [NIP-89 - Recommended Application Handlers](https://github.com/nostr-protocol/nips/blob/master/89.md). Keep in mind that a customer giving feedback may, in fact, be another DVM and not a human.
* `e`, `p`, `k`: tags that are defined in the [NIP-25 - Reactions](https://github.com/nostr-protocol/nips/blob/8331354947f2d577e13eb5da4a56133071cb1019/25.md) spec.
* NOTE: If the input params requires input to be encrypted, then `content` field will have encrypted payload with `p` tag as key.