From 7202571a17d906fba7515a6e8ac6a36464ffaa2a Mon Sep 17 00:00:00 2001 From: haorendashu <385321165@qq.com> Date: Fri, 11 Oct 2024 08:39:46 +0800 Subject: [PATCH 1/2] Update 94 add a d tag to event Add a d tag to file metadata event and it will make this event replacable. It means that the file can moving between media services. --- 94.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/94.md b/94.md index a057cb2d8..a2495947a 100644 --- a/94.md +++ b/94.md @@ -31,6 +31,7 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr { "kind": 1063, "tags": [ + ["d",], ["url",], ["m", ], ["x",], @@ -55,3 +56,9 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr * A relay for indexing shared files. For example, to promote torrents. * A pinterest-like client where people can share their portfolio and inspire others. * A simple way to distribute configurations and software updates. +* Use as a movable media for notes. + 1. Clients upload a file to media service and get a file link and other file infomations. + 2. Clients send a File Metadata event and this event must contain a ```d``` tag, it means that this event is replacable. + 3. If a client want to sends notes with this file, it should imports this event with ```nostr:naddr``` style uri. + 4. When other clients vist a note with kind 1063 naddr style uri, it should find this event and display it like a normal media file. + 5. If this file's owner want to change the media service, he can upload this file to other media service and resend a File Metadata event with the same ```d``` tag. From 8e14c531bddcd17ccf29bc5021f5276e40fc9f7e Mon Sep 17 00:00:00 2001 From: haorendashu <385321165@qq.com> Date: Fri, 11 Oct 2024 19:02:13 +0800 Subject: [PATCH 2/2] Update nip-94 change replaceable to addressable --- 94.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/94.md b/94.md index a2495947a..dcddf7ef5 100644 --- a/94.md +++ b/94.md @@ -58,7 +58,7 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr * A simple way to distribute configurations and software updates. * Use as a movable media for notes. 1. Clients upload a file to media service and get a file link and other file infomations. - 2. Clients send a File Metadata event and this event must contain a ```d``` tag, it means that this event is replacable. + 2. Clients send a File Metadata event and this event must contain a ```d``` tag, it means that this event is addressable. 3. If a client want to sends notes with this file, it should imports this event with ```nostr:naddr``` style uri. 4. When other clients vist a note with kind 1063 naddr style uri, it should find this event and display it like a normal media file. 5. If this file's owner want to change the media service, he can upload this file to other media service and resend a File Metadata event with the same ```d``` tag.