nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-14 07:49:07 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 1078.md

Browse Source
This commit is contained in:
BlowaterNostr 2023-07-15 00:14:53 +08:00 committed by GitHub
parent 3beaca87c8
commit 399b92153a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 19 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
1078.md
View File

@ -1,2 +1,19 @@
# Customized Application Data, but as a regular events
Everything is the same as NIP78, except it's a regular event kind 1078 so that replays don't remove the old event.
# NIP-1078
## Arbitrary custom app data
`draft` `optional` `author:BlowaterNostr`
## Nostr event
This NIP specifies the use of event kind `1078` which is almost identical to 30078 except that it's not a replacible event.
## Some use cases
The reason to not having a 30078 is that some clients want to implement local state changes as CRDTs, meaning support cumulative and associative mutations.
Meaning the order of applying operations doesn't change the final result as long as the same set of operations are applied.
For example, in [Blowater](https://blowater.deno.dev), Pin/Unpin Contacts is implemented as regular events to achieve better consistency.
Event set [`Pin Npub X`, `Unpin NpubX`, `Pin Npub Y`] will result in a pin list of `[Y]` no matter how the order is shifted.
Many other operations are best implemented as CRDTs as well.