From 1026260cda54fb8eb345417c18b7dfd10a1a766a Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Fri, 15 May 2026 16:44:53 -0300 Subject: [PATCH] rename to F4. --- 54.md => F4.md | 30 +----------------------------- 1 file changed, 1 insertion(+), 29 deletions(-) rename 54.md => F4.md (79%) diff --git a/54.md b/F4.md similarity index 79% rename from 54.md rename to F4.md index 81b3a063..71617a37 100644 --- a/54.md +++ b/F4.md @@ -1,4 +1,4 @@ -NIP-54 +NIP-F4 ====== Podcasts @@ -50,31 +50,3 @@ Podcast episodes are `kind:54` with some tags: "sig": "...", } ``` - -### Podcast Comments - -These are normal text comments like `kind:1`, but specific for podcast episodes. - -```jsonc -{ - "id": "606f6c703f04c70806a5c2830e3853bd83c44985b1f282a070ba894add3724b0", - "pubkey": "b2c5d5bf69d14d35c25fa47d5c67896b13394136734065a371c5bf2c62f905d2", - "kind": 55, - "created_at": 1700682556, - "tags": [ - ["e", "55807e7d5cd90d0303d7dce7397f996fdbaed8697903f326c7cf8ad999b9de3d"], - ], - "content": "", - "sig": "...", -} -``` - -(It's unclear if it's best to use this or a generic kind for commenting on stuff that isn't `kind:1`.) - -### Reactions (likes), zaps and reposts - -These work normally according to their own NIPs. - -### To be added: - -- "read" events, signaling that a user has listened to a given podcast, perhaps just use https://github.com/nostr-protocol/nips/pull/933