diff options
| -rw-r--r-- | 02.md | 2 | ||||
| -rw-r--r-- | 51.md | 2 |
2 files changed, 4 insertions, 0 deletions
| @@ -27,6 +27,8 @@ For example: | |||
| 27 | 27 | ||
| 28 | 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. | 28 | 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. |
| 29 | 29 | ||
| 30 | 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. | ||
| 31 | |||
| 30 | ## Uses | 32 | ## Uses |
| 31 | 33 | ||
| 32 | ### Follow list backup | 34 | ### Follow list backup |
| @@ -10,6 +10,8 @@ This NIP defines lists of things that users can create. Lists can contain refere | |||
| 10 | 10 | ||
| 11 | 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`. | 11 | 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`. |
| 12 | 12 | ||
| 13 | 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. | ||
| 14 | |||
| 13 | ## Types of lists | 15 | ## Types of lists |
| 14 | 16 | ||
| 15 | ## Standard lists | 17 | ## Standard lists |