From 79c97843091558754e5e389218de86dbdfd1db94 Mon Sep 17 00:00:00 2001 From: Dustin Dannenhauer Date: Fri, 12 Jan 2024 10:07:42 +0000 Subject: [PATCH] Update 89.md with preferred feedback format --- 89.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/89.md b/89.md index 43d197fc..389feadc 100644 --- a/89.md +++ b/89.md @@ -58,7 +58,8 @@ The third value of the tag SHOULD be the platform where this recommendation migh ["web", "https://..../a/", "nevent"], ["web", "https://..../p/", "nprofile"], ["web", "https://..../e/"], - ["ios", ".../"] + ["ios", ".../"], + ["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.