nip17: "seen" event.

03.md

@@ -12,8 +12,8 @@ This NIP defines an event with `kind:1040` that can contain an [OpenTimestamps](
 {
   "kind": 1040
   "tags": [
-    ["e", <target-event-id>, <relay-url>],
-    ["k", "<target-event-kind>"]
+    ["e", <event-id>, <relay-url>],
+    ["alt", "opentimestamps attestation"]
   ],
   "content": <base64-encoded OTS file data>
 }

17.md

@@ -8,7 +8,11 @@ Private Direct Messages
 
 This NIP defines an encrypted direct messaging scheme using [NIP-44](44.md) encryption and [NIP-59](59.md) seals and gift wraps.
 
-## Direct Message Kind
+## Message kinds
+
+Each of these message kinds can be gift-wrapped as described afterwards. Clients have to first unwrap them to then see their kinds.
+
+### Direct Message Kind
 
 Kind `14` is a chat message. `p` tags identify one or more receivers of the message.
 
@@ -31,7 +35,7 @@ Kind `14` is a chat message. `p` tags identify one or more receivers of the mess
 
 `.content` MUST be plain text. Fields `id` and `created_at` are required.
 
-An `e` tag denotes the direct parent message this post is replying to. 
+An `e` tag denotes the direct parent message this post is replying to.
 
 `q` tags MAY be used when citing events in the `.content` with [NIP-21](21.md).
 
@@ -41,7 +45,7 @@ An `e` tag denotes the direct parent message this post is replying to.
 
 Kind `14`s MUST never be signed. If it is signed, the message might leak to relays and become **fully public**.
 
-## File Message Kind
+### File Message Kind
 
 ```jsonc
 {
@@ -59,7 +63,6 @@ Kind `14`s MUST never be signed. If it is signed, the message might leak to rela
     ["decryption-key", "<decryption-key>"],
     ["decryption-nonce", "<decryption-nonce>"],
     ["x", "<the SHA-256 hexencoded string of the file>"],
-    // rest of tags...
   ],
   "content": "<file-url>"
 }
@@ -82,6 +85,46 @@ Kind `15` is used for sending encrypted file event messages:
 
 Just like kind `14`, kind `15`s MUST never be signed.
 
+### "Seen" event
+
+An event of kind `30016` that CAN be emitted automatically by a client whenever a chat window is displayed to the user, even if the user hasn't acted on it.
+
+```jsonc
+{
+  "id": "<usual hash>",
+  "pubkey": "<sender-pubkey>",
+  "created_at": "<current-time>",
+  "kind": 30016,
+  "tags": [
+    ["d", "<subject>"],
+    ["seen", "<latest_message_id>", "<previous_id>", "<...>"]
+  ],
+  "content": ""
+}
+```
+
+- `d` must be set to the conversation subject, or it can be empty or omitted in the most common case of a `<subject>` not existing.
+- `seen` must be set to the id of the last messages seen. It can contain any number of ids, ordered from the newest to the oldest.
+
+This event SHOULD be discarded whenever a new event is received for the same conversation.
+
+Any messages with timestamp before the last item in the `seen` array are assumed to have been seen.
+
+If there is a gap in the `seen` array that indicates a message may have been missed for whatever reason.
+
+For example:
+
+- `alice` sends message `aaaa`
+- `alice` sends message `bbbb`
+- `alice` sends message `cccc`
+- `bob` sends event with `["seen", "bbbb", "aaaa"]`
+- at this point `alice`'s client should display `aaaa` and `bbbb` as seen, `cccc` as unseen
+- `alice` sends message `dddd`
+- `alice` sends message `eeee`, which is lost due to relay malfunction
+- `alice` sends message `ffff`
+- `bob` sends event with `["seen", "ffff", "dddd", "cccc"]`
+- at this point `alice`'s client should display all messages as seen, except for `eeee` which should be displayed with an error indicator
+
 ## Chat Rooms
 
 The set of `pubkey` + `p` tags defines a chat room. If a new `p` tag is added or a current one is removed, a new room is created with a clean message history.

18.md

@@ -40,5 +40,6 @@ Since `kind 6` reposts are reserved for `kind 1` contents, we use `kind 16`
 as a "generic repost", that can include any kind of event inside other than
 `kind 1`.
 
-`kind 16` reposts SHOULD contain a `"k"` tag with the stringified kind number
+`kind 16` reposts SHOULD contain a `k` tag with the stringified kind number
 of the reposted event as its value.
+

25.md

@@ -26,6 +26,8 @@ There SHOULD be a `p` tag set to the `pubkey` of the event being reacted to. If
 
 If the event being reacted to is an addressable event, an `a` SHOULD be included together with the `e` tag, it must be set to the coordinates (`kind:pubkey:d-tag`) of the event being reacted to.
 
+The reaction SHOULD include a `k` tag with the stringified kind number of the reacted event as its value.
+
 The `e` and `a` tags SHOULD include relay and pubkey hints. The `p` tags SHOULD include relay hints.
 
 The reaction event MAY include a `k` tag with the stringified kind number of the reacted event as its value.

57.md

@@ -37,7 +37,6 @@ In addition, the event MAY include the following tags:
 
 - `e` is an optional hex-encoded event id. Clients MUST include this if zapping an event rather than a person.
 - `a` is an optional event coordinate that allows tipping addressable events such as NIP-23 long-form notes.
-- `k` is the stringified kind of the target event.
 
 Example:
 
@@ -50,8 +49,7 @@ Example:
     ["amount", "21000"],
     ["lnurl", "lnurl1dp68gurn8ghj7um5v93kketj9ehx2amn9uh8wetvdskkkmn0wahz7mrww4excup0dajx2mrv92x9xp"],
     ["p", "04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"],
-    ["e", "9ae37aa68f48645127299e9453eb5d908a0cbb6058ff340d528ed4d37c8994fb"],
-    ["k", "1"]
+    ["e", "9ae37aa68f48645127299e9453eb5d908a0cbb6058ff340d528ed4d37c8994fb"]
   ],
   "pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
   "created_at": 1679673265,
@@ -153,7 +151,6 @@ Example `zap receipt`:
       ["p", "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"],
       ["P", "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"],
       ["e", "3624762a1274dd9636e0c552b53086d70bc88c165bc4dc0f9e836a1eaf86c3b8"],
-      ["k", "1"],
       ["bolt11", "lnbc10u1p3unwfusp5t9r3yymhpfqculx78u027lxspgxcr2n2987mx2j55nnfs95nxnzqpp5jmrh92pfld78spqs78v9euf2385t83uvpwk9ldrlvf6ch7tpascqhp5zvkrmemgth3tufcvflmzjzfvjt023nazlhljz2n9hattj4f8jq8qxqyjw5qcqpjrzjqtc4fc44feggv7065fqe5m4ytjarg3repr5j9el35xhmtfexc42yczarjuqqfzqqqqqqqqlgqqqqqqgq9q9qxpqysgq079nkq507a5tw7xgttmj4u990j7wfggtrasah5gd4ywfr2pjcn29383tphp4t48gquelz9z78p4cq7ml3nrrphw5w6eckhjwmhezhnqpy6gyf0"],
       ["description", "{\"pubkey\":\"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322\",\"content\":\"\",\"id\":\"d9cc14d50fcb8c27539aacf776882942c1a11ea4472f8cdec1dea82fab66279d\",\"created_at\":1674164539,\"sig\":\"77127f636577e9029276be060332ea565deaf89ff215a494ccff16ae3f757065e2bc59b2e8c113dd407917a010b3abd36c8d7ad84c0e3ab7dab3a0b0caa9835d\",\"kind\":9734,\"tags\":[[\"e\",\"3624762a1274dd9636e0c552b53086d70bc88c165bc4dc0f9e836a1eaf86c3b8\"],[\"p\",\"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245\"],[\"relays\",\"wss://relay.damus.io\",\"wss://nostr-relay.wlvs.space\",\"wss://nostr.fmt.wiz.biz\",\"wss://relay.nostr.bg\",\"wss://nostr.oxtr.dev\",\"wss://nostr.v0l.io\",\"wss://brb.io\",\"wss://nostr.bitcoiner.social\",\"ws://monad.jb55.com:8080\",\"wss://relay.snort.social\"]]}"],
       ["preimage", "5d006d2cf1e73c7148e7519a4c68adc81642ce0e25a432b2434c99f97344c15f"]

61.md

@@ -53,7 +53,6 @@ Clients MUST prefix the public key they P2PK-lock with `"02"` (for nostr<>cashu
         [ "proof", "{\"amount\":1,\"C\":\"02277c66191736eb72fce9d975d08e3191f8f96afb73ab1eec37e4465683066d3f\",\"id\":\"000a93d6f8a1d2c4\",\"secret\":\"[\\\"P2PK\\\",{\\\"nonce\\\":\\\"b00bdd0467b0090a25bdf2d2f0d45ac4e355c482c1418350f273a04fedaaee83\\\",\\\"data\\\":\\\"02eaee8939e3565e48cc62967e2fde9d8e2a4b3ec0081f29eceff5c64ef10ac1ed\\\"}]\"}" ],
         [ "u", "https://stablenut.umint.cash" ],
         [ "e", "<nutzapped-event-id>", "<relay-hint>" ],
-        [ "k", "<nutzapped-kind>"],
         [ "p", "e9fbced3a42dcf551486650cc752ab354347dd413b307484e4fd1818ab53f991" ], // recipient of nutzap
     ]
 }

A0.md

@@ -1,60 +0,0 @@
-NIP-A0
-======
-
-Voice Messages
------------
-
-**Status:** Draft
-
-This NIP defines new events `kind: 1222` for root messages and `kind: 1244` for reply messages to be used for short voice messages, typically up to 60 seconds in length.
-
-## Specification
-
-### Event Kind `1222` and Kind `1244`
-
-The `kind: 1222` event is defined as follows:
-
--   `content`: MUST be a URL pointing directly to an audio file.
-    -   The audio file SHOULD be in `audio/mp4` (.m4a) format using AAC or Opus encoding. Clients MAY support other common audio formats like `audio/ogg`, `audio/webm`, or `audio/mpeg` (mp3), but `audio/mp4` is recommended for broad compatibility and efficiency.
-    -   The audio duration SHOULD be no longer than 60 seconds. Clients publishing `kind: 1222` events SHOULD enforce this limit or provide a clear warning to the user if exceeded.
--   `tags`:
-    -   Tags MAY be included as per other NIPs (e.g., `t` for hashtags, `g` for geohash, etc.).
-
-  The `kind: 1244` event is defined as follows:
-  
--    To be used for replies, `kind: 1244` events MUST follow the structure of `NIP-22`.
--   `content`: MUST be a URL pointing directly to an audio file.
-    -   The audio file SHOULD be in `audio/mp4` (.m4a) format using AAC or Opus encoding. Clients MAY support other common audio formats like `audio/ogg`, `audio/webm`, or `audio/mpeg` (mp3), but `audio/mp4` is recommended for broad compatibility and efficiency.
-    -   The audio duration SHOULD be no longer than 60 seconds. Clients publishing `kind: 1222` events SHOULD enforce this limit or provide a clear warning to the user if exceeded.
--   `tags`:
-    -   Tags MAY be included as per other NIPs (e.g., `t` for hashtags, `g` for geohash, etc.).
-
-
-## Visual representation with `imeta` (NIP-92) tag (optional)
-
-The following imeta (NIP-92) tags MAY be included so clients can render a visual preview without having to download the audio file first:
-
-- `waveform`: amplitude values over time, space separated full integers, less than 100 values should be enough to render a nice visual
-- `duration`: audio length in seconds
-
-## Examples
-
-### Root Voice Message Example
-
-```json
-{
-  "content": "https://blossom.primal.net/5fe7df0e46ee6b14b5a8b8b92939e84e3ca5e3950eb630299742325d5ed9891b.mp4",
-  "created_at": 1752501052,
-  "id": "...",
-  "kind": 1222,
-  "pubkey": "...",
-  "sig": "...",
-  "tags": [
-    [
-      "imeta",
-      "url https://blossom.primal.net/5fe7df0e46ee6b14b5a8b8b92939e84e3ca5e3950eb630299742325d5ed9891b.mp4",
-      "waveform 0 7 35 8 100 100 49 8 4 16 8 10 7 2 20 10 100 100 100 100 100 100 15 100 100 100 25 60 5 4 3 1 0 100 100 15 100 29 88 0 33 11 39 100 100 19 4 100 42 35 5 0 1 5 0 0 11 38 100 94 17 11 44 58 5 100 100 100 55 14 72 100 100 57 6 1 14 2 16 100 100 40 16 100 100 6 32 14 13 41 36 16 14 6 3 0 1 2 1 6 0",
-      "duration 8"
-    ]
-  ]
-}

README.md

@@ -102,7 +102,6 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 - [NIP-96: HTTP File Storage Integration](96.md)
 - [NIP-98: HTTP Auth](98.md)
 - [NIP-99: Classified Listings](99.md)
-- [NIP-A0: Voice Messages](A0.md)
 - [NIP-B0: Web Bookmarks](B0.md)
 - [NIP-B7: Blossom](B7.md)
 - [NIP-C0: Code Snippets](C0.md)
@@ -152,8 +151,6 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `1063`        | File Metadata                   | [94](94.md)                            |
 | `1068`        | Poll                            | [88](88.md)                            |
 | `1111`        | Comment                         | [22](22.md)                            |
-| `1222`        | Voice Message                   | [A0](A0.md)                            |
-| `1244`        | Voice Message Comment           | [A0](A0.md)                            |
 | `1311`        | Live Chat Message               | [53](53.md)                            |
 | `1337`        | Code Snippet                    | [C0](C0.md)                            |
 | `1617`        | Patches                         | [34](34.md)                            |
@@ -201,9 +198,9 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `10063`       | User server list                | [Blossom][blossom]                     |
 | `10096`       | File storage server list        | [96](96.md)                            |
 | `10166`       | Relay Monitor Announcement      | [66](66.md)                            |
-| `10312`       | Room Presence                   | [53](53.md)                            |
 | `13194`       | Wallet Info                     | [47](47.md)                            |
 | `17375`       | Cashu Wallet Event              | [60](60.md)                            |
+| `17375`       | Ecash Mint Recommendation       | [87](87.md)                            |
 | `21000`       | Lightning Pub RPC               | [Lightning.Pub][lnpub]                 |
 | `22242`       | Client Authentication           | [42](42.md)                            |
 | `23194`       | Wallet Request                  | [47](47.md)                            |
@@ -235,8 +232,6 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `30166`       | Relay Discovery                 | [66](66.md)                            |
 | `30267`       | App curation sets               | [51](51.md)                            |
 | `30311`       | Live Event                      | [53](53.md)                            |
-| `30312`       | Interactive Room                | [53](53.md)                            |
-| `30313`       | Conference Event                | [53](53.md)                            |
 | `30315`       | User Statuses                   | [38](38.md)                            |
 | `30388`       | Slide Set                       | [Corny Chat][cornychat-slideset]       |
 | `30402`       | Classified Listing              | [99](99.md)                            |