nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 17:05:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

No "d tag" is required for "Event 78"

Browse Source
This commit is contained in:
tiltpapa 2024-01-26 18:37:27 +09:00
parent 44751b549f
commit 3eec5b2d8e
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
78.md
View File

@ -8,11 +8,7 @@ Arbitrary custom app data
This NIP defines some events that do not require interoperability. This NIP defines some events that do not require interoperability.
The common points are the following two points, and the difference is the kind. ### Event `30078`: remoteStorage-like Event
- 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
The goal of this kind is to enable [remoteStorage](https://remotestorage.io/)-like capabilities for custom applications that do not care about interoperability. 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 - 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 - 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. 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**: **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.