diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-01-04 10:34:24 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-01-04 10:34:24 -0300 |
| commit | 8c3c42171503fd07e24bb8681fc01419974a2ac0 (patch) | |
| tree | 22a9eee9f2023d83b594fb5b691c516ec667097b /35.md | |
| parent | 4472f9bbd951db084d1ce460b8b00d7de0c5e154 (diff) | |
merge NIP-35 into NIP-05.
Diffstat (limited to '35.md')
| -rw-r--r-- | 35.md | 43 |
1 files changed, 0 insertions, 43 deletions
| @@ -1,43 +0,0 @@ | |||
| 1 | |||
| 2 | NIP-35 | ||
| 3 | ====== | ||
| 4 | |||
| 5 | User Discovery | ||
| 6 | -------------- | ||
| 7 | |||
| 8 | `draft` `optional` `author:mikedilger` | ||
| 9 | |||
| 10 | This NIP extends NIP-05 to facilitate a mechanism of user discovery that provides both public key information and relay information. | ||
| 11 | |||
| 12 | This NIP does not modify any data or events within the nostr protocol. It only extends the contents of `https://<domain>/.well-known/nostr.json?name=<local-part>` return values with additional relay information. | ||
| 13 | |||
| 14 | With this NIP implemented, clients may then attempt to discover users via email-like addresses (see NIP-05) and potentially find what relays they post to along with their public key. | ||
| 15 | |||
| 16 | ### nostr.json contents | ||
| 17 | |||
| 18 | NIP-05 specifies a `nostr.json` file with contents like this (refer to NIP-05): | ||
| 19 | |||
| 20 | ```json | ||
| 21 | { | ||
| 22 | "names": { | ||
| 23 | "bob": "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9" | ||
| 24 | } | ||
| 25 | } | ||
| 26 | ``` | ||
| 27 | |||
| 28 | This NIP proposes an optional additional key like this: | ||
| 29 | |||
| 30 | ```` | ||
| 31 | { | ||
| 32 | "names": { | ||
| 33 | "bob": "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9" | ||
| 34 | }, | ||
| 35 | "relays": { | ||
| 36 | "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9": [ "wss://relay.example.com", "wss://relay2.example.com" ] | ||
| 37 | } | ||
| 38 | } | ||
| 39 | ```` | ||
| 40 | |||
| 41 | The `relays` key contains an object with public keys as properties and arrays of relays as values. | ||
| 42 | |||
| 43 | Web servers which serve nostr.json files dynamically responding to the query string SHOULD also serve the relays data for any name they serve in the same reply. | ||