From 0146892501d63042d13724bae7c887bfa985e251 Mon Sep 17 00:00:00 2001 From: Alex Gleason Date: Thu, 7 Dec 2023 10:01:57 -0600 Subject: NIP-02: Rename Contact List to Follow List --- 02.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to '02.md') diff --git a/02.md b/02.md index 0653d06..8c47a5f 100644 --- a/02.md +++ b/02.md @@ -1,12 +1,12 @@ NIP-02 ====== -Contact List and Petnames -------------------------- +Follow List +----------- `final` `optional` -A special event with kind `3`, meaning "contact list" is defined as having a list of `p` tags, one for each of the followed/known profiles one is following. +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>,
, ]`. The `content` can be anything and should be ignored. @@ -25,27 +25,27 @@ For example: } ``` -Every new contact list that gets published overwrites the past ones, so it should contain all entries. Relays and clients SHOULD delete past contact lists as soon as they receive a new one. +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. ## Uses -### Contact list backup +### Follow list backup If one believes a relay will store their events for sufficient time, they can use this kind-3 event to backup their following list and recover on a different device. ### Profile discovery and context augmentation -A client may rely on the kind-3 event to display a list of followed people by profiles one is browsing; make lists of suggestions on who to follow based on the contact lists of other people one might be following or browsing; or show the data in other contexts. +A client may rely on the kind-3 event to display a list of followed people by profiles one is browsing; make lists of suggestions on who to follow based on the follow lists of other people one might be following or browsing; or show the data in other contexts. ### Relay sharing -A client may publish a full list of contacts with good relays for each of their contacts so other clients may use these to update their internal relay lists if needed, increasing censorship-resistance. +A client may publish a follow list with good relays for each of their follows so other clients may use these to update their internal relay lists if needed, increasing censorship-resistance. ### Petname scheme -The data from these contact lists can be used by clients to construct local ["petname"](http://www.skyhunter.com/marcs/petnames/IntroPetNames.html) tables derived from other people's contact lists. This alleviates the need for global human-readable names. For example: +The data from these follow lists can be used by clients to construct local ["petname"](http://www.skyhunter.com/marcs/petnames/IntroPetNames.html) tables derived from other people's follow lists. This alleviates the need for global human-readable names. For example: -A user has an internal contact list that says +A user has an internal follow list that says ```json [ @@ -53,7 +53,7 @@ A user has an internal contact list that says ] ``` -And receives two contact lists, one from `21df6d143fb96c2ec9d63726bf9edc71` that says +And receives two follow lists, one from `21df6d143fb96c2ec9d63726bf9edc71` that says ```json [ -- cgit v1.2.3