From a20add84da4ceca3a67082ed21e30fe7043b4b6d Mon Sep 17 00:00:00 2001 From: Arman The Parman <77603167+ArmanTheParman@users.noreply.github.com> Date: Tue, 18 Jun 2024 15:44:07 +1000 Subject: [PATCH 1/2] follow list rewording A suggesting to make readability better. --- 02.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/02.md b/02.md index 4029b222..d7772a2d 100644 --- a/02.md +++ b/02.md @@ -6,9 +6,13 @@ 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. +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 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>,
, ]`. +Each "p" tag entry should be populated as follows: +- The first element is "p" +- The second element contains the pubkey string +- The third element is either an empty string, or a relay URL where events from that key can be found +- The fourth and final element is either an empty string or a string with a local name for that profile (or "petname") The `.content` is not used. @@ -27,7 +31,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. From 850025478fcc26fe12a11b1abaeb49ad030a8fb9 Mon Sep 17 00:00:00 2001 From: Arman The Parman <77603167+ArmanTheParman@users.noreply.github.com> Date: Wed, 19 Jun 2024 13:04:27 +1000 Subject: [PATCH 2/2] Update 02.md Fewer words, as suggested. --- 02.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/02.md b/02.md index d7772a2d..0c921dd5 100644 --- a/02.md +++ b/02.md @@ -8,14 +8,9 @@ Follow List 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 be populated as follows: -- The first element is "p" -- The second element contains the pubkey string -- The third element is either an empty string, or a relay URL where events from that key can be found -- The fourth and final element is either an empty string or a string with a local name for that profile (or "petname") - -The `.content` is not used. - +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