From 3eec5b2d8e29a1ebec6d09703ce98c1d9aae432d Mon Sep 17 00:00:00 2001 From: tiltpapa Date: Fri, 26 Jan 2024 18:37:27 +0900 Subject: [PATCH] No "d tag" is required for "Event 78" --- 78.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/78.md b/78.md index cf1ccc4..467464a 100644 --- a/78.md +++ b/78.md @@ -8,11 +8,7 @@ Arbitrary custom app data This NIP defines some events that do not require interoperability. -The common points are the following two points, and the difference is the kind. - - With a `d` tag containing some reference to the app name and context -- or any other arbitrary string. - - `content` and other `tags` can be anything or in any format. - -### Event `30078`: remoteStorage-like event +### Event `30078`: remoteStorage-like Event The goal of this kind is to enable [remoteStorage](https://remotestorage.io/)-like capabilities for custom applications that do not care about interoperability. @@ -28,10 +24,10 @@ This NIP specifies the use of event kind `30078` (parameterized replaceable even - A way for client developers to propagate dynamic parameters to users without these having to update - Personal private data generated by apps that have nothing to do with Nostr, but allow users to use Nostr relays as their personal database -### Event `78`: Versatile event +### Event `78`: Versatile Event When creating Nostr-based applications, suggesting a new kinds each time can be burdensome for developers. For purposes like testing or for applications that do not require interoperability, it is acceptable to use the defined event here. **Nostr event**: -This NIP specifies the use of event kind `78` with a `d` tag containing some reference to the app name and context -- or any other arbitrary string. `content` and other `tags` can be anything or in any format. +This NIP specifies the use of event kind `78` (regular event). `content` and other `tags` can be anything or in any format.