add nipB0, social bookmarking.

2025-12-09 08:38:50 +00:00 · 2025-04-23 10:20:27 -03:00
13 changed files with 70 additions and 176 deletions
--- a/21.md
+++ b/21.md
@@ -12,27 +12,9 @@ The scheme is `nostr:`.

 The identifiers that come after are expected to be the same as those defined in [NIP-19](19.md) (except `nsec`).

-#### Examples
+## Examples

 - `nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9`
 - `nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpp4mhxue69uhhytnc9e3k7mgpz4mhxue69uhkg6nzv9ejuumpv34kytnrdaksjlyr9p`
 - `nostr:note1fntxtkcy9pjwucqwa9mddn7v03wwwsu9j330jj350nvhpky2tuaspk6nqc`
 - `nostr:nevent1qqstna2yrezu5wghjvswqqculvvwxsrcvu7uc0f78gan4xqhvz49d9spr3mhxue69uhkummnw3ez6un9d3shjtn4de6x2argwghx6egpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5nxnepm`
-
-### Linking HTML pages to Nostr entities
-
-`<link>` tags with `rel="alternate"` can be used to associate webpages to Nostr events, in cases where the same content is served via the two mediums (for example, a web server that exposes Markdown articles both as HTML pages and as `kind:30023' events served under itself as a relay or through some other relay). For example:
-
-```
-<head>
-  <link rel="alternate" href="nostr:naddr1qqyrzwrxvc6ngvfkqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823cph95ag" />
-</head>
-```
-
-Likewise, `<link>` tags with `rel="me"` or `rel="author"` can be used to assign authorship of webpages to Nostr profiles. For example:
-
-```
-<head>
-  <link rel="me" href="nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyd8wumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6qpq80cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwswpnfsn" />
-</head>
-```
--- a/22.md
+++ b/22.md
@@ -18,9 +18,9 @@ and `p` for the author of the parent item.

 ```jsonc
 {
-  "kind": 1111,
-  "content": "<comment>",
-  "tags": [
+  kind: 1111,
+  content: '<comment>',
+  tags: [
    // root scope: event addresses, event ids, or I-tags.
    ["<A, E, I>", "<address, id or I-value>", "<relay or web page hint>", "<root event's pubkey, if an E tag>"],
    // the root item kind
@@ -64,9 +64,9 @@ A comment on a blog post looks like this:

 ```jsonc
 {
-  "kind": 1111,
-  "content": "Great blog post!",
-  "tags": [
+  kind: 1111,
+  content: 'Great blog post!',
+  tags: [
    // top-level comments scope to event addresses or ids
    ["A", "30023:3c9849383bdea883b0bd16fece1ed36d37e37cdde3ce43b17ea4e9192ec11289:f9347ca7", "wss://example.relay"],
    // the root kind
@@ -91,9 +91,9 @@ A comment on a [NIP-94](94.md) file looks like this:

 ```jsonc
 {
-  "kind": 1111,
-  "content": "Great file!",
-  "tags": [
+  kind: 1111,
+  content: 'Great file!',
+  tags: [
    // top-level comments have the same scope and reply to addresses or ids
    ["E", "768ac8720cdeb59227cf95e98b66560ef03d8bc9a90d721779e76e68fb42f5e6", "wss://example.relay", "3721e07b079525289877c366ccab47112bdff3d1b44758ca333feb2dbbbbe5bb"],
    // the root kind
@@ -115,9 +115,9 @@ A reply to a comment looks like this:

 ```jsonc
 {
-  "kind": 1111,
-  "content": "This is a reply to \"Great file!\"",
-  "tags": [
+  kind: 1111,
+  content: 'This is a reply to "Great file!"',
+  tags: [
    // nip-94 file event id
    ["E", "768ac8720cdeb59227cf95e98b66560ef03d8bc9a90d721779e76e68fb42f5e6", "wss://example.relay", "fd913cd6fa9edb8405750cd02a8bbe16e158b8676c0e69fdc27436cc4a54cc9a"],
    // the root kind
@@ -138,9 +138,9 @@ A comment on a website's url looks like this:

 ```jsonc
 {
-  "kind": 1111,
-  "content": "Nice article!",
-  "tags": [
+  kind: 1111,
+  content: 'Nice article!',
+  tags: [
    // referencing the root url
    ["I", "https://abc.com/articles/1"],
    // the root "kind": for an url, the kind is its domain
@@ -159,11 +159,11 @@ A podcast comment example:

 ```jsonc
 {
-  "id": "80c48d992a38f9c445b943a9c9f1010b396676013443765750431a9004bdac05",
-  "pubkey": "252f10c83610ebca1a059c0bae8255eba2f95be4d1d7bcfa89d7248a82d9f111",
-  "kind": 1111,
-  "content": "This was a great episode!",
-  "tags": [
+  id: "80c48d992a38f9c445b943a9c9f1010b396676013443765750431a9004bdac05",
+  pubkey: "252f10c83610ebca1a059c0bae8255eba2f95be4d1d7bcfa89d7248a82d9f111",
+  kind: 1111,
+  content: "This was a great episode!",
+  tags: [
    // podcast episode reference
    ["I", "podcast:item:guid:d98d189b-dc7b-45b1-8720-d4b98690f31f", "https://fountain.fm/episode/z1y9TMQRuqXl2awyrQxg"],
    // podcast episode type
@@ -181,9 +181,9 @@ A reply to a podcast comment:

 ```jsonc
 {
-  "kind": 1111,
-  "content": "I'm replying to the above comment.",
-  "tags": [
+  kind: 1111,
+  content: "I'm replying to the above comment.",
+  tags: [
    // podcast episode reference
    ["I", "podcast:item:guid:d98d189b-dc7b-45b1-8720-d4b98690f31f", "https://fountain.fm/episode/z1y9TMQRuqXl2awyrQxg"],
    // podcast episode type
--- a/26.md
+++ b/26.md
@@ -1,5 +1,3 @@
-> __Warning__  `unrecommended`: adds unecessary burden for little gain
-
 NIP-26
 =======

--- a/61.md
+++ b/61.md
@@ -46,10 +46,10 @@ Clients MUST prefix the public key they P2PK-lock with `"02"` (for nostr<>cashu

 ```jsonc
 {
-    "kind": 9321,
-    "content": "Thanks for this great idea.",
-    "pubkey": "<sender-pubkey>",
-    "tags": [
+    kind: 9321,
+    content: "Thanks for this great idea.",
+    pubkey: "<sender-pubkey>",
+    tags: [
        [ "proof", "{\"amount\":1,\"C\":\"02277c66191736eb72fce9d975d08e3191f8f96afb73ab1eec37e4465683066d3f\",\"id\":\"000a93d6f8a1d2c4\",\"secret\":\"[\\\"P2PK\\\",{\\\"nonce\\\":\\\"b00bdd0467b0090a25bdf2d2f0d45ac4e355c482c1418350f273a04fedaaee83\\\",\\\"data\\\":\\\"02eaee8939e3565e48cc62967e2fde9d8e2a4b3ec0081f29eceff5c64ef10ac1ed\\\"}]\"}" ],
        [ "u", "https://stablenut.umint.cash" ],
        [ "e", "<nutzapped-event-id>", "<relay-hint>" ],
--- a/66.md
+++ b/66.md
@@ -1,8 +1,4 @@
-NIP-66
-======
-
-Relay Discovery and Liveness Monitoring
-------------------
+# NIP-66: Relay Discovery and Liveness Monitoring

 `draft` `optional`

--- a/69.md
+++ b/69.md
@@ -1,8 +1,6 @@
-NIP-69
-======
+# NIP-69

-Peer-to-peer Order events
-------------------------
+## Peer-to-peer Order events

 `draft` `optional`

--- a/84.md
+++ b/84.md
@@ -23,7 +23,7 @@ or obvious non-useful information from the query string.
 ### Attribution
 Clients MAY include one or more `p` tags, tagging the original authors of the material being highlighted; this is particularly
 useful when highlighting non-nostr content for which the client might be able to get a nostr pubkey somehow
-(e.g. prompting the user or reading a `<link rel="me" href="nostr:nprofile1..." />` tag on the document). A role MAY be included as the
+(e.g. prompting the user or reading a `<meta name="nostr:nprofile1..." />` tag on the document). A role MAY be included as the
 last value of the tag.

 ```jsonc
--- a/88.md
+++ b/88.md
@@ -1,8 +1,6 @@
-NIP-88
-======
+# NIP-88

-Polls
-----
+## Polls

 `draft` `optional`

--- a/B0.md
+++ b/B0.md
@@ -1,61 +0,0 @@
-NIP-B0
-======
-
-Web Bookmarking
---------------
-
-`draft` `optional`
-
-This NIP defines `kind:39701` (an _addressable event_) for a URI as a web bookmark which uses the HTTP (Hypertext transfer protocol) scheme.
-These web bookmark events are _addressable_ and deletable per [NIP-09](09.md).
-
-### Editability
-
-Web bookmarks are meant to be editable, so they should include a `d` tag with an identifier for the bookmark. Clients should take care to only publish and read these events from relays that implement that. If they don't do that they should also take care to hide old versions of the same bookmark they may receive.
-
-### Format
-
-The format uses an _addressable event_ of `kind:39701`.
-
-The `.content` of these events should be a detailed description of the web bookmark. It is required but can be an empty string.
-
-The `d` tag is required.
-
-In this way web bookmarks events can be queried by the `d` tag by clients, which is just their URL without the scheme, which is always and everywhere assumed to be `https://` or `http://`.
-
-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.
-
-### Metadata
-
-For the date of the last update the `.created_at` field should be used. For "tags"/"hashtags" (i.e. topics about which the event might be of relevance) the `t` tag should be used.
-
-Other metadata fields can be added as tags to the event as necessary.
-
-* `"published_at"`, for the timestamp in unix seconds (stringified) of the first time the bookmark was published
-* `"title"`, title about bookmark and can be used as a attribute for the HTML link element
-
-## Example event 
-
-```jsonc
-{
-  "kind": 39701,
-  "id": "d7a92714f81d0f712e715556aee69ea6da6bfb287e6baf794a095d301d603ec7",
-  "pubkey": "2729620da105979b22acfdfe9585274a78c282869b493abfa4120d3af2061298",
-  "created_at": 1738869705,
-  "tags": [
-    // Required tags
-    ["d", "alice.blog/post"],
-    // Optional tags    
-    ["published_at", "1738863000"],
-    ["title", "Blog insights by Alice"],  
-    ["t", "post"],
-    ["t", "insight"]
-  ],
-  "content": "A marvelous insight by Alice about the nature of blogs and posts.",
-  "sig": "36d34e6448fe0223e9999361c39c492a208bc423d2fcdfc2a3404e04df7c22dc65bbbd62dbe8a4373c62e4d29aac285b5aa4bb9b4b8053bd6207a8b45fbd0c98"
-}
-```
-
-### Replies & Comments
-
-Replies to `kind 39701` MUST use `kind 1111` events as comments with [NIP-22](22.md).
--- a/B7.md
+++ b/B7.md
@@ -1,41 +0,0 @@
-NIP-B7
-======
-
-Blossom media
-------------
-
-`draft` `optional`
-
-This NIP specifies how Nostr clients can use [Blossom][] for handling media.
-
-Blossom is a set of standards (called BUDs) for dealing with servers that store files addressable by their SHA-256 sums. Nostr clients may make use of all the BUDs for allowing users to upload files, manage their own files and so on, but most importantly Nostr clients SHOULD make use of [BUD-03][] to fetch `kind:10063` lists of servers for each user:
-
-```json
-{
-  "id": "e4bee088334cb5d38cff1616e964369c37b6081be997962ab289d6c671975d71",
-  "pubkey": "781208004e09102d7da3b7345e64fd193cd1bc3fce8fdae6008d77f9cabcd036",
-  "content": "",
-  "kind": 10063,
-  "created_at": 1708774162,
-  "tags": [
-    ["server", "https://blossom.self.hosted"],
-    ["server", "https://cdn.blossom.cloud"]
-  ],
-  "sig": "cc5efa74f59e80622c77cacf4dd62076bcb7581b45e9acff471e7963a1f4d8b3406adab5ee1ac9673487480e57d20e523428e60ffcc7e7a904ac882cfccfc653"
-}
-```
-
-Whenever a Nostr client finds a URL in an event published by a given user and that URL ends a 64-character hex string (with or without an ending file extension) and that URL is not available anymore, that means that string is likely a representation of a sha256 and that the user may have a `kind:10063` list of Blossom servers published.
-
-Given that, the client SHOULD look into the `kind:10063` list for other Blossom servers and lookup for the same 64-character hex string in them, by just using the hex string as a path (optionally with the file extension at the end), producing a URL like `https://blossom.self.hosted/<hex-string>.png`.
-
-When downloading such files Nostr clients SHOULD verify that the sha256-hash of its contents matches the 64-character hex string.
-
-More information can be found at [BUD-03][].
-
-### More complex interactions
-
-Clients may use other facilities exposed by Blossom servers (for example, for checking if a file exists in a Blossom server, instead of actually downloading it) which are better documented in the [BUDs][Blossom].
-
-[Blossom]: https://github.com/hzrd149/blossom
-[BUD-03]: https://github.com/hzrd149/blossom/blob/master/buds/03.md
--- a/C0.md
+++ b/C0.md
@@ -1,8 +1,4 @@
-NIP-C0
-======
-
-Code Snippets
-------------
+# NIP-C0: Code Snippets

 `draft` `optional`

--- a/README.md
+++ b/README.md
@@ -44,7 +44,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 - [NIP-23: Long-form Content](23.md)
 - [NIP-24: Extra metadata fields and tags](24.md)
 - [NIP-25: Reactions](25.md)
- [NIP-26: Delegated Event Signing](26.md) --- **unrecommended**: adds unecessary burden for little gain
+- [NIP-26: Delegated Event Signing](26.md)
 - [NIP-27: Text Note References](27.md)
 - [NIP-28: Public Chat](28.md)
 - [NIP-29: Relay-based Groups](29.md)
@@ -89,7 +89,6 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 - [NIP-73: External Content IDs](73.md)
 - [NIP-75: Zap Goals](75.md)
 - [NIP-78: Application-specific data](78.md)
- [NIP-7D: Threads](7D.md)
 - [NIP-84: Highlights](84.md)
 - [NIP-86: Relay Management API](86.md)
 - [NIP-88: Polls](88.md)
@@ -100,8 +99,7 @@ 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-B0: Web Bookmarks](B0.md)
- [NIP-B7: Blossom](B7.md)
+- [NIP-7D: Threads](7D.md)
 - [NIP-C0: Code Snippets](C0.md)
 - [NIP-C7: Chats](C7.md)

@@ -249,7 +247,6 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `34550`       | Community Definition            | [72](72.md)                            |
 | `38383`       | Peer-to-peer Order events       | [69](69.md)                            |
 | `39000-9`     | Group metadata events           | [29](29.md)                            |
-| `39701`       | Web bookmarks                   | [B0](B0.md)                            |

 [NUD: Custom Feeds]: https://wikifreedia.xyz/cip-01/
 [nostrocket]: https://github.com/nostrocket/NIPS/blob/main/Problems.md
@@ -344,7 +341,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `preimage`        | hash of `bolt11` invoice             | --                              | [57](57.md)                                        |
 | `price`           | price                                | currency, frequency             | [99](99.md)                                        |
 | `proxy`           | external ID                          | protocol                        | [48](48.md)                                        |
-| `published_at`    | unix timestamp (string)              | --                              | [23](23.md), [B0](B0.md)                           |
+| `published_at`    | unix timestamp (string)              | --                              | [23](23.md)                                        |
 | `relay`           | relay url                            | --                              | [42](42.md), [17](17.md)                           |
 | `relays`          | relay list                           | --                              | [57](57.md)                                        |
 | `repo`            | Reference to the origin repository   | --                              | [C0](C0.md)                                        |
@@ -353,7 +350,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `subject`         | subject                              | --                              | [14](14.md), [17](17.md), [34](34.md)              |
 | `summary`         | summary                              | --                              | [23](23.md), [52](52.md)                           |
 | `thumb`           | badge thumbnail                      | dimensions in pixels            | [58](58.md)                                        |
-| `title`           | title                                | --                              | [23](23.md), [B0](B0.md)                           |
+| `title`           | article title                        | --                              | [23](23.md)                                        |
 | `tracker`         | torrent tracker URL                  | --                              | [35](35.md)                                        |
 | `web`             | webpage URL                          | --                              | [34](34.md)                                        |
 | `zap`             | pubkey (hex), relay URL              | weight                          | [57](57.md)                                        |
--- a/b0.md
+++ b/b0.md
@@ -0,0 +1,31 @@
+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).