From 4eb4b1392772e35d3ae8473bb0641e387711d0c9 Mon Sep 17 00:00:00 2001 From: pablof7z Date: Fri, 21 Mar 2025 12:55:42 +0000 Subject: [PATCH 1/2] adds that clients shouldnt publish contradictory handlers --- 89.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/89.md b/89.md index 24aa3c57..83798e70 100644 --- a/89.md +++ b/89.md @@ -74,6 +74,17 @@ Using a `k` tag(s) (instead of having the kind of the `d` tag) provides: Multiple tags might be registered by the app, following NIP-19 nomenclature as the second value of the array. +No contradictory hints can appear. Apps should not publish handlers with the same `platform:type` duple. + +For example: an event with: + +```jsonc +["web", "https://.../path1/", "nevent"], +["web", "https://.../path2/", "nevent"], +``` + +where the `web` + `nevent` duple is duplicated with contradictory values is invalid and clients SHOULD ignore it. + 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. # Client tag From 92c2176c1702cf378ade99f63e0fadb1426fb78d Mon Sep 17 00:00:00 2001 From: pablof7z Date: Fri, 21 Mar 2025 12:58:47 +0000 Subject: [PATCH 2/2] a bit more explicit --- 89.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/89.md b/89.md index 83798e70..f9a9dd69 100644 --- a/89.md +++ b/89.md @@ -85,6 +85,8 @@ For example: an event with: where the `web` + `nevent` duple is duplicated with contradictory values is invalid and clients SHOULD ignore it. +Applications that have different URLs should use different `kind:31990` to announce the different URLs that should be used per kind. + 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. # Client tag