add nip34-related follow lists.

51.md

@@ -39,6 +39,8 @@ For example, _mute list_ can contain the public keys of spammers and bad actors
 | DM relays         | 10050 | Where to receive [NIP-17](17.md) direct messages            | `"relay"` (see [NIP-17](17.md))                                                                     |
 | Good wiki authors | 10101 | [NIP-54](54.md) user recommended wiki authors               | `"p"` (pubkeys)                                                                                     |
 | Good wiki relays  | 10102 | [NIP-54](54.md) relays deemed to only host useful articles  | `"relay"` (relay URLs)                                                                              |
+| Git authors       | 10017 | code (people who produce NIP-34 events) follow list         | `"p"` (pubkeys -- with optional relay hint and petname)                                             |
+| Git repositories  | 10018 | [NIP-34](34.md) followed repositories                       | `"a"` (kind:30617 repository announcement event)                                                    |
 
 ### Sets
 
@@ -52,7 +54,7 @@ Aside from their main identifier, the `"d"` tag, sets can optionally have a `"ti
 | ---                   | ---   | ---                                                                                          | ---                                                                                 |
 | Follow sets           | 30000 | categorized groups of users a client may choose to check out in different circumstances      | `"p"` (pubkeys)                                                                     |
 | Relay sets            | 30002 | user-defined relay groups the user can easily pick and choose from during various operations | `"relay"` (relay URLs)                                                              |
-| Bookmark sets         | 30003 | user-defined bookmarks categories , for when bookmarks must be in labeled separate groups    | `"e"` (kind:1 notes), `"a"` (kind:30023 articles)                                   |
+| Bookmark sets         | 30003 | user-defined bookmarks categories , for when bookmarks must be in labeled separate groups    | `"e"` (kind:1 notes), `"a"` (kind:30023 articles), `"t"` (hashtags), `"r"` (URLs)   |
 | Curation sets         | 30004 | groups of articles picked by users as interesting and/or belonging to the same category      | `"a"` (kind:30023 articles), `"e"` (kind:1 notes)                                   |
 | Curation sets         | 30005 | groups of videos picked by users as interesting and/or belonging to the same category        | `"e"` (kind:21 videos)                                                              |
 | Kind mute sets        | 30007 | mute pubkeys by kinds<br>`"d"` tag MUST be the kind string                                   | `"p"` (pubkeys)                                                                     |

52.md

@@ -65,8 +65,6 @@ Example:
     ["d", "<random-identifier>"],
 
     ["title", "<title of calendar event>"],
-    ["summary", "<brief description of the calendar event>"],
-    ["image", "<string with image URI>"],
 
     // dates
     ["start", "<YYYY-MM-DD>"],
@@ -95,6 +93,8 @@ Aside from the common tags, this also takes the following tags:
 
 * `start` (required) inclusive start Unix timestamp in seconds. Must be less than `end`, if it exists.
 * `end` (optional) exclusive end Unix timestamp in seconds. If omitted, the calendar event ends instantaneously.
+* `start_tzid` (optional) time zone of the start timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`
+* `end_tzid` (optional) time zone of the end timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`. If omitted and `start_tzid` is provided, the time zone of the end timestamp is the same as the start timestamp.
 
 ```yaml
 {
@@ -114,6 +114,9 @@ Aside from the common tags, this also takes the following tags:
     ["start", "<unix timestamp in seconds>"],
     ["end", "<unix timestamp in seconds>"],
 
+    ["start_tzid", "<IANA Time Zone Database identifier>"],
+    ["end_tzid", "<IANA Time Zone Database identifier>"],
+
     // location
     ["location", "<location>"],
     ["g", "<geohash>"],

59.md

@@ -99,8 +99,6 @@ AUTH, and refuse to serve wrapped events to non-recipients.
 
 When adding expiration tags to both `seal` and `gift wrap` layers, implementations SHOULD use independent random timestamps for each layer. Using different `created_at` values increases timing variance and helps protect against metadata correlation attacks.
 
-Since signing keys are random, relays SHOULD delete `kind 1059` events whose p-tag matches the signer of
-[NIP-09](09.md) deletions or [NIP-62](62.md) vanish requests.
 
 ## An Example
 

C0.md

@@ -23,9 +23,9 @@ The `.content` field contains the actual code snippet text.
 - `extension` - File extension (without the dot). Examples: "js", "py", "rs"
 - `description` - Brief description of what the code does
 - `runtime` - Runtime or environment specification (e.g., "node v18.15.0", "python 3.11")
-- `license` - License under which the code (along with any related data contained within the event, when available, such as the description) is shared. This MUST be a standard [SPDX](https://spdx.org/licenses/) short identifier (e.g., "MIT", "GPL-3.0-or-later", "Apache-2.0") when available. An additional parameter containing a reference to the actual text of the license MAY be provided. This tag can be repeated, to indicate multi-licensing, allowing recipients to use the code under any license of choosing among the referenced ones
+- `license` - License under which the code is shared (e.g., "MIT", "GPL-3.0", "Apache-2.0")
 - `dep` - Dependency required for the code to run (can be repeated)
-- `repo` - Reference to a repository where this code originates. This MUST be a either standard URL or, alternatively, the address of a [NIP-34](34.md) Git repository annoucement event in the form `"30617:<32-bytes hex a pubkey>:<d tag value>"`. If a repository announcement is referenced, a recommended relay URL where to find the event should be provided as an additional parameter
+- `repo` - Reference to a repository where this code originates
 
 ## Format