From 95961e680f640004818f8516d4d51bdfb25141be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A2u=20Cao?= Date: Wed, 22 Apr 2026 15:37:45 +0400 Subject: [PATCH] Add rationale for kind numbers --- doc/nostr/nip-place-photos.md | 4 ++++ doc/nostr/nip-place-reviews.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/doc/nostr/nip-place-photos.md b/doc/nostr/nip-place-photos.md index 352e0c5..b08746e 100644 --- a/doc/nostr/nip-place-photos.md +++ b/doc/nostr/nip-place-photos.md @@ -102,6 +102,10 @@ Clients SHOULD include `alt` (accessibility descriptions), `dim` (dimensions), ` ## Rationale +### Kind 360 + +Easy to remember as a 360-degree view of places. + ### Why not use NIP-68 (Picture-first feeds)? NIP-68 is designed for general-purpose social feeds (like Instagram). Place photos require strict guarantees about what entity is being depicted to be useful for map clients, directories, and review aggregators. By mandating the `i` tag for POI linking and the `g` tag for spatial querying, this kind ensures interoperability for geo-spatial applications without cluttering general picture feeds with mundane POI images (like photos of storefronts or menus). diff --git a/doc/nostr/nip-place-reviews.md b/doc/nostr/nip-place-reviews.md index 177d6d9..dd22229 100644 --- a/doc/nostr/nip-place-reviews.md +++ b/doc/nostr/nip-place-reviews.md @@ -276,6 +276,10 @@ Content payloads SHOULD NOT include place identifiers. ## Rationale +### Kind 30360 + +Pairs with kind 360 (Place Photos). Easy to remember as a 360-degree review of all aspects of a place. + ### No Place Field in Content Avoids duplication and inconsistency with tags.