nostr
/
nips
mirror of https://github.com/nostr-protocol/nips.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NIP-02, NIP-51: new tags should be added to the end of the list 

Fixes https://github.com/nostr-protocol/nips/issues/958
This commit is contained in:
Alex Gleason 2024-01-01 12:21:50 -06:00
parent 27fef638e2
commit 3d8652ea14
No known key found for this signature in database
GPG Key ID: 7211D1F99744FBB7
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
02.md
View File

@ -27,6 +27,8 @@ For example:
Every new following list that gets published overwrites the past ones, so it should contain all entries. Relays and clients SHOULD delete past following lists as soon as they receive a new one.
Whenever new follows are added to an existing list, clients SHOULD append them to the end of the list, so they are stored in chronological order.
## Uses
### Follow list backup

2
51.md
View File

@ -10,6 +10,8 @@ This NIP defines lists of things that users can create. Lists can contain refere
Public items in a list are specified in the event `tags` array, while private items are specified in a JSON array that mimics the structure of the event `tags` array, but stringified and encrypted using the same scheme from [NIP-04](04.md) (the shared key is computed using the author's public and private key) and stored in the `.content`.
When new items are added to an existing list, clients SHOULD append them to the end of the list, so they are stored in chronological order.
## Types of lists
## Standard lists