remove tzid from calendar event.

18.md

@@ -36,10 +36,3 @@ as a "generic repost", that can include any kind of event inside other than
 
 `kind 16` reposts SHOULD contain a `"k"` tag with the stringified kind number
 of the reposted event as its value.
-
-When reposting a replaceable event, the repost SHOULD include an `"a"` tag with
-the event coordinate (`kind:pubkey:d-tag`) of the reposted event.
-
-If the `"a"` tag is not present, it indicates that a specific version of a replaceable
-event is being reposted, in which case the `content` field must contain the full
-JSON string of the reposted event.

51.md

@@ -26,7 +26,7 @@ For example, _mute list_ can contain the public keys of spammers and bad actors
 | Mute list         | 10000 | things the user doesn't want to see in their feeds          | `"p"` (pubkeys), `"t"` (hashtags), `"word"` (lowercase string), `"e"` (threads)                     |
 | Pinned notes      | 10001 | events the user intends to showcase in their profile page   | `"e"` (kind:1 notes)                                                                                |
 | Read/write relays | 10002 | where a user publishes to and where they expect mentions    | see [NIP-65](65.md)                                                                                 |
-| Bookmarks         | 10003 | uncategorized, "global" list of things a user wants to save | `"e"` (kind:1 notes), `"a"` (kind:30023 articles)                   |
+| Bookmarks         | 10003 | uncategorized, "global" list of things a user wants to save | `"e"` (kind:1 notes), `"a"` (kind:30023 articles), `"t"` (hashtags), `"r"` (URLs)                   |
 | Communities       | 10004 | [NIP-72](72.md) communities the user belongs to             | `"a"` (kind:34550 community definitions)                                                            |
 | Public chats      | 10005 | [NIP-28](28.md) chat channels the user is in                | `"e"` (kind:40 channel definitions)                                                                 |
 | Blocked relays    | 10006 | relays clients should never connect to                      | `"relay"` (relay URLs)                                                                              |

52.md

@@ -65,6 +65,8 @@ 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>"],
@@ -93,8 +95,6 @@ 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,9 +114,6 @@ 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>"],

EE.md

@@ -1,8 +1,6 @@
-NIP-EE
+# NIP-EE
-======
 
-E2EE Messaging using the Messaging Layer Security (MLS) Protocol
+## E2EE Messaging using the Messaging Layer Security (MLS) Protocol
-----------------------------------------------------------------
 
 `draft` `optional`