Add guidelines tag to NIP-29 group metadata

11.md

@@ -21,10 +21,6 @@ When a relay receives an HTTP(s) request with an `Accept` header of `application
   "supported_nips": <a list of NIP numbers supported by the relay>,
   "software": <string identifying relay software URL>,
   "version": <string version identifier>
-  "privacy_policy": <a link to a text file describing the relay's privacy policy>,
-  "terms_of_service": <a link to a text file describing the relay's term of service>,
-
-
 }
 ```
 
@@ -78,30 +74,21 @@ The relay server implementation MAY be provided in the `software` attribute.  If
 
 The relay MAY choose to publish its software version as a string attribute.  The string format is defined by the relay implementation.  It is recommended this be a version number or commit identifier.
 
-### Privacy Policy
-
-The relay owner/admin MAY choose to link to a privacy policy document, which describes how the relay utilizes user data. Data collection, data usage, data retention, monetization of data, and third party data sharing SHOULD be included.
-
-### Terms of Service
-
-The relay owner/admin MAY choose to link to a terms of service document.
-
-
-
 Extra Fields
 ------------
 
 ### Server Limitations
 
 These are limitations imposed by the relay on clients. Your client
-should expect that requests exceed these *practical* limitations
+should expect that requests which exceed these *practical* limitations
 are rejected or fail immediately.
 
 ```jsonc
 {
   "limitation": {
     "max_message_length": 16384,
-    "max_subscriptions": 300,
+    "max_subscriptions": 20,
+    "max_filters": 100,
     "max_limit": 5000,
     "max_subid_length": 100,
     "max_event_tags": 100,
@@ -111,30 +98,33 @@ are rejected or fail immediately.
     "payment_required": true,
     "restricted_writes": true,
     "created_at_lower_limit": 31536000,
-    "created_at_upper_limit": 3,
-    "default_limit": 500
+    "created_at_upper_limit": 3
   },
   // other fields...
 }
 ```
 
-- `max_message_length`: the maximum number of bytes for incoming JSON that the relay
+- `max_message_length`: this is the maximum number of bytes for incoming JSON that the relay
 will attempt to decode and act upon. When you send large subscriptions, you will be
 limited by this value. It also effectively limits the maximum size of any event. Value is
-calculated from `[` to `]` after UTF-8 serialization (so some unicode characters
+calculated from `[` to `]` and is after UTF-8 serialization (so some unicode characters
 will cost 2-3 bytes). It is equal to the maximum size of the WebSocket message frame.
 
 - `max_subscriptions`: total number of subscriptions that may be
-active on a single websocket connection to this relay. Authenticated clients with a (paid) relationship to the relay
+active on a single websocket connection to this relay. It's possible
+that authenticated clients with a (paid) relationship to the relay
 may have higher limits.
 
+- `max_filters`: maximum number of filter values in each subscription.
+Must be one or higher.
+
 - `max_subid_length`: maximum length of subscription id as a string.
 
 - `max_limit`: the relay server will clamp each filter's `limit` value to this number.
 This means the client won't be able to get more than this number
 of events from a single subscription filter. This clamping is typically done silently
 by the relay, but with this number, you can know that there are additional results
-if you narrow your filter's time range or other parameters.
+if you narrowed your filter's time range or other parameters.
 
 - `max_event_tags`: in any event, this is the maximum number of elements in the `tags` list.
 
@@ -152,7 +142,7 @@ Even if set to False, authentication may be required for specific actions.
 
 - `payment_required`: this relay requires payment before a new connection may perform any action.
 
-- `restricted_writes`: this relay requires some kind of condition to be fulfilled to
+- `restricted_writes`: this relay requires some kind of condition to be fulfilled in order to
 accept events (not necessarily, but including `payment_required` and `min_pow_difficulty`).
 This should only be set to `true` when users are expected to know the relay policy before trying
 to write to it -- like belonging to a special pubkey-based whitelist or writing only events of
@@ -162,8 +152,6 @@ a specific niche kind or content. Normal anti-spam heuristics, for example, do n
 
 - `created_at_upper_limit`: 'created_at' upper limit
 
-- `default_limit`: The maximum returned events if you send a filter with the limit set to 0.
-
 ### Event Retention
 
 There may be a cost associated with storing data forever, so relays
@@ -224,7 +212,7 @@ flexibility is up to the client software.
 ```
 
 - `relay_countries`: a list of two-level ISO country codes (ISO 3166-1 alpha-2)  whose
-  laws and policies may affect this relay. `EU` may be used for European Union countries. A `*` can be used for global relays.
+  laws and policies may affect this relay. `EU` may be used for European Union countries.
 
 Remember that a relay may be hosted in a country which is not the
 country of the legal entities who own the relay, so it's very
@@ -249,7 +237,7 @@ To support this goal, relays MAY specify some of the following values.
 
 - `language_tags` is an ordered list
   of [IETF language tags](https://en.wikipedia.org/wiki/IETF_language_tag) indicating
-  the major languages spoken on the relay. A `*` can be used for global relays.
+  the major languages spoken on the relay.
 
 - `tags` is a list of limitations on the topics to be discussed.
   For example `sfw-only` indicates that only "Safe For Work" content
@@ -288,82 +276,49 @@ Relays that require payments may want to expose their fee schedules.
 
 ### Examples
 
-As of 25 March 2025 the following command provided these results:
+As of 2 May 2023 the following command provided these results:
 
 ```bash
-curl -H "Accept: application/nostr+json" https://jellyfish.land | jq
+$ curl -H "Accept: application/nostr+json" https://eden.nostr.land | jq
 ```
 
 ```json
 {
-  "name": "JellyFish",
-  "description": "Stay Immortal!",
-  "banner": "https://image.nostr.build/7fdefea2dec1f1ec25b8ce69362566c13b2b7f13f1726c2e4584f05f64f62496.jpg",
-  "pubkey": "bf2bee5281149c7c350f5d12ae32f514c7864ff10805182f4178538c2c421007",
-  "contact": "hi@dezh.tech",
-  "software": "https://github.com/dezh-tech/immortal",
+  "description": "nostr.land family of relays (us-or-01)",
+  "name": "nostr.land",
+  "pubkey": "52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
+  "software": "custom",
   "supported_nips": [
     1,
+    2,
+    4,
     9,
     11,
-    13,
-    17,
-    40,
-    42,
-    59,
-    62,
-    70
+    12,
+    16,
+    20,
+    22,
+    28,
+    33,
+    40
   ],
-  "version": "immortal - 0.0.9",
-  "relay_countries": [
-    "*"
-  ],
-  "language_tags": [
-    "*"
-  ],
-  "tags": [],
-  "posting_policy": "https://jellyfish.land/tos.txt",
-  "payments_url": "https://jellyfish.land/relay",
-  "icon": "https://image.nostr.build/2547e9ec4b23589e09bc7071e0806c3d4293f76284c58ff331a64bce978aaee8.jpg",
-  "retention": [],
+  "version": "1.0.1",
+  "limitation": {
+    "payment_required": true,
+    "max_message_length": 65535,
+    "max_event_tags": 2000,
+    "max_subscriptions": 20,
+    "auth_required": false
+  },
+  "payments_url": "https://eden.nostr.land",
   "fees": {
     "subscription": [
       {
-        "amount": 3000,
-        "period": 2628003,
-        "unit": "sats"
-      },
-      {
-        "amount": 8000,
-        "period": 7884009,
-        "unit": "sats"
-      },
-      {
-        "amount": 15000,
-        "period": 15768018,
-        "unit": "sats"
-      },
-      {
-        "amount": 28000,
-        "period": 31536036,
-        "unit": "sats"
+        "amount": 2500000,
+        "unit": "msats",
+        "period": 2592000
       }
     ]
   },
-  "limitation": {
-    "auth_required": false,
-    "max_message_length": 70000,
-    "max_subid_length": 256,
-    "max_subscriptions": 350,
-    "min_pow_difficulty": 0,
-    "payment_required": true,
-    "restricted_writes": true,
-    "max_event_tags": 2000,
-    "max_content_length": 70000,
-    "created_at_lower_limit": 0,
-    "created_at_upper_limit": 2147483647,
-    "default_limit": 500,
-    "max_limit": 5000
-  }
 }
 ```

29.md

@@ -153,6 +153,7 @@ When this event is not found, clients may still connect to the group, but treat
     ["name", "Pizza Lovers"],
     ["picture", "https://pizza.com/pizza.png"],
     ["about", "a group for people who love pizza"],
+    ["guidelines", "Rule #1: No pineapple"]
     ["public"], // or ["private"]
     ["open"] // or ["closed"]
   ]
@@ -160,7 +161,7 @@ When this event is not found, clients may still connect to the group, but treat
 }
 ```
 
-`name`, `picture` and `about` are basic metadata for the group for display purposes. `public` signals the group can be _read_ by anyone, while `private` signals that only AUTHed users can read. `open` signals that anyone can request to join and the request will be automatically granted, while `closed` signals that members must be pre-approved or that requests to join will be manually handled.
+`name`, `picture`, `about`, and `guidelines` are basic metadata for the group for display purposes. `public` signals the group can be _read_ by anyone, while `private` signals that only AUTHed users can read. `open` signals that anyone can request to join and the request will be automatically granted, while `closed` signals that members must be pre-approved or that requests to join will be manually handled.
 
 - *group admins* (`kind:39001`) (optional)
 

65.md

@@ -6,9 +6,11 @@ Relay List Metadata
 
 `draft` `optional`
 
-Defines a replaceable event using `kind:10002` to advertise relays where the user generally **writes** to and relays where the user generally **reads** mentions.
+Defines a replaceable event using `kind:10002` to advertise preferred relays for discovering a user's content and receiving fresh content from others.
 
-The event MUST include a list of `r` tags with relay URLs as value and an optional `read` or `write` marker. If the marker is omitted, the relay is both **read** and **write**.
+The event MUST include a list of `r` tags with relay URIs and a `read` or `write` marker. Relays marked as `read` / `write` are called READ / WRITE relays, respectively. If the marker is omitted, the relay is used for both purposes.
+
+The `.content` is not used.
 
 ```jsonc
 {
@@ -24,19 +26,45 @@ The event MUST include a list of `r` tags with relay URLs as value and an option
 }
 ```
 
-When downloading events **from** a user, clients SHOULD use the **write** relays of that user.
+This NIP doesn't fully replace relay lists that are designed to configure a client's usage of relays (such as `kind:3` style relay lists). Clients MAY use other relay lists in situations where a `kind:10002` relay list cannot be found.
 
-When downloading events **about** a user, where the user was tagged (mentioned), clients SHOULD use the user's **read** relays.
+## When to Use Read and Write Relays
 
-When publishing an event, clients SHOULD:
+When seeking events **from** a user, Clients SHOULD use the WRITE relays of the user's `kind:10002`.
 
-- Send the event to the **write** relays of the author
-- Send the event to all **read** relays of each tagged user
+When seeking events **about** a user, where the user was tagged, Clients SHOULD use the READ relays of the user's `kind:10002`.
 
-### Size
+When broadcasting an event, Clients SHOULD:
 
-Clients SHOULD guide users to keep `kind:10002` lists small (2-4 relays of each category).
+- Broadcast the event to the WRITE relays of the author
+- Broadcast the event to all READ relays of each tagged user
 
-### Discoverability
+## Motivation
 
-Clients SHOULD spread an author's `kind:10002` event to as many relays as viable, paying attention to relays that, at any moment, serve naturally as well-known public indexers for these relay lists (where most other clients and users are connecting to in order to publish and fetch those).
+The old model of using a fixed relay list per user centralizes in large relay operators: 
+
+  - Most users submit their posts to the same highly popular relays, aiming to achieve greater visibility among a broader audience
+  - Many users are pulling events from a large number of relays in order to get more data at the expense of duplication
+  - Events are being copied between relays, oftentimes to many different relays
+  
+This NIP allows Clients to connect directly with the most up-to-date relay set from each individual user, eliminating the need of broadcasting events to popular relays. 
+
+## Final Considerations
+
+1. Clients SHOULD guide users to keep `kind:10002` lists small (2-4 relays). 
+
+2. Clients SHOULD spread an author's `kind:10002` event to as many relays as viable. 
+
+3. `kind:10002` events should primarily be used to advertise the user's preferred relays to others. A user's own client may use other heuristics for selecting relays for fetching data.
+
+4. DMs SHOULD only be broadcasted to the author's WRITE relays and to the receiver's READ relays to keep maximum privacy. 
+
+5. If a relay signals support for this NIP in their [NIP-11](11.md) document that means they're willing to accept kind 10002 events from a broad range of users, not only their paying customers or whitelisted group.
+
+6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-6).
+
+7. When publishing to a relay, clients SHOULD ensure the user's `kind 10002` is also available on that relay. Relays SHOULD accept and serve `kind 10002` notes for any pubkey whose notes they store. Relays MAY scrape the network for missing `kind 10002` events. The goal here is that for any note served from a relay the user can also request the author's relay selections as a way of bootstrapping further context discovery.
+
+## Related articles
+- [Outbox model](https://mikedilger.com/gossip-model/)
+- [What is the Outbox Model?](https://habla.news/u/hodlbod@coracle.social/8YjqXm4SKY-TauwjOfLXS)

7D.md

@@ -6,14 +6,15 @@ Threads
 
 `draft` `optional`
 
-A thread is a `kind 11` event.  Threads SHOULD include a `title`.
+A thread is a `kind 11` event.  Threads SHOULD include a `subject` with a summary
+of the thread's topic.
 
 ```json
 {
   "kind": 11,
   "content": "Good morning",
   "tags": [
-    ["title", "GM"]
+    ["subject", "GM"]
   ]
 }
 ```

84.md

@@ -40,12 +40,3 @@ last value of the tag.
 ### Context
 Clients MAY include a `context` tag, useful when the highlight is a subset of a paragraph and displaying the
 surrounding content might be beneficial to give context to the highlight.
-
-## Quote Highlights
-A `comment` tag may be added to create a quote highlight. This MUST be rendered like a quote repost with the highlight as the quoted note.
-
-This is to prevent the creation and multiple notes (highlight + kind 1) for a single highlight action, which looks bad in micro-blogging clients where these notes may appear in succession.
-
-p-tag mentions MUST have a `mention` attribute to distinguish it from authors and editors.
-
-r-tag urls from the comment MUST have a `mention` attribute to distinguish from the highlighted source url. The source url MUST have the `source` attribute.

b0.md

@@ -1,31 +0,0 @@
-NIP-B0
-======
-
-Web Bookmarking
----------------
-
-`draft` `optional`
-
-This NIP defines `kind:39701` as website bookmarks.
-
-```jsonc
-{
-  "kind": 39701,
-  "id": "d7a92714f81d0f712e715556aee69ea6da6bfb287e6baf794a095d301d603ec7",
-  "pubkey": "2729620da105979b22acfdfe9585274a78c282869b493abfa4120d3af2061298",
-  "created_at": 1738869705,
-  "tags": [
-    ["d", "alice.blog/post"],
-    ["t", "post"],
-    ["t", "insight"]
-  ],
-  "content": "A marvelous insight by Alice about the nature of blogs and posts.",
-  "sig": "36d34e6448fe0223e9999361c39c492a208bc423d2fcdfc2a3404e04df7c22dc65bbbd62dbe8a4373c62e4d29aac285b5aa4bb9b4b8053bd6207a8b45fbd0c98"
-}
-```
-
-Bookmarks can be queried by the `d` tag, which is just their URL without the scheme, which is always and everywhere assumed to be `https://`.
-
-The querystring and the hash must be removed entirely, unless their requirement is explicitly stated either by the user or by some hardcoded list of URLs that rely on querystrings for basic routing provided by the client (I've searched the internet extensively and could only find 3 websites that do this: YouTube, Hacker News and a random guy's sad old blog).
-
-Bookmarks can be commented on with [NIP-22](22.md).