diff --git a/82.md b/82.md index 250ecf40..75d00c37 100644 --- a/82.md +++ b/82.md @@ -19,6 +19,7 @@ The description and visuals of an application are optionally provided via a link "tags": [ ["d", ""], // Usually reverse domain notation: com.example.app ["name", ""], // Name, in case wiki article is missing + ["icon", ""], // Icon URL: https://cdn.zap.store/8a8fc42aed83d76ccb48afd6eec40bb8b15af6296e03a27a9eeab015f07e2a54.png ["repository", ""], // Source code repository URL: https://github.com/example/android ["commit-id", ""], // SHA1 commit id used to build the release ["a", "30818::", ""], // Pointer to NIP-54 wiki article @@ -30,9 +31,9 @@ The description and visuals of an application are optionally provided via a link All tags are optional except for `d`. Android applications MUST use the application identifier as the `d` tag. -The `content` field SHOULD be empty. +The `content` field SHOULD be empty. For `icon` any URL is valid but a Blossom [BUD-01](https://github.com/hzrd149/blossom/blob/master/buds/01.md#get-sha256---get-blob) endpoint is recommended. -Clients SHOULD first check for the availability of the linked kind 30818 to retrieve the app description and display information contained in tags including `title`, `summary`, `image`, `icon`, `url`, `t`, etc. +Clients SHOULD first check for the availability of the linked kind 30818 to retrieve the app description and display information contained in tags including `title`, `summary`, `image`, `icon`, `url`, `t`, etc. The `name` field MUST be used as fallback if `title` was not available. Note on [NIP-89](89.md): Not all applications can or should handle nostr events. Those that do MAY choose to publish a NIP-89 event.