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

kind 30079 to 7978

Browse Source
This commit is contained in:
tshinohara 2024-09-29 15:00:09 +09:00
parent 5f8b7e5e50
commit b282b236bf
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
78.md
View File

@ -14,7 +14,7 @@ Even though interoperability is great, some apps do not want or do not need inte
This NIP specifies the use of event kind `30078` (an _addressable_ 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.
It is assumed that `30078` replaces the event itself when retrieved by a d tag. In contrast, we define `30079` as a continuous set of data. Events with the a `d` tag are not replaced, but treated as continuous data.
It is assumed that `30078` replaces the event itself when retrieved by a d tag. In contrast, we define `7078` as a continuous set of data. Events with the a `d` tag are not replaced, but treated as continuous data.
## Some use cases
@ -24,7 +24,7 @@ It is assumed that `30078` replaces the event itself when retrieved by a d tag.
- 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
### kind 30079
### kind 7078
- Count the number of posts to the relay per hour
- Bitcoin Chart