nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-29 16:31:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge 850025478f into a551c5b693

Browse Source
This commit is contained in:
Arman The Parman 2024-06-25 14:20:38 -03:00 committed by GitHub
commit d795d758c7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
02.md
View File

@ -6,12 +6,11 @@ Follow List
`final` `optional`
A special event with kind `3`, meaning "follow list" is defined as having a list of `p` tags, one for each of the followed/known profiles one is following.
Each tag entry should contain the key for the profile, a relay URL where events from that key can be found (can be set to an empty string if not needed), and a local name (or "petname") for that profile (can also be set to an empty string or not provided), i.e., `["p", <32-bytes hex key>, <main relay URL>, <petname>]`.
The `.content` is not used.
A special event with kind `3`, meaning "follow list", is defined as having a list of `p` tags, one for each of the profiles to be followed.
Each "p" tag entry should have a pubkey string as the second element.
The third and fourth elements can be empty strings, or the relay URL and "petname", respectively.
The `.content` key is not used.
For example:
```json
@ -27,7 +26,7 @@ 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.
Every new following list that gets published overwrites all previous 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.