diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-02-09 17:13:35 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-02-09 17:13:35 -0300 |
| commit | d87763781dc1213d7c1b53ab0a4172f8237cbdf3 (patch) | |
| tree | 3f10e0ff3074242c9c92b6329d5fd5eef4103240 | |
| parent | 6d55463c89e6c944bcd49c93f90b16a0ce5fce1e (diff) | |
clarify and change account account_uris to account_paths.
| -rw-r--r-- | 05.md | 8 |
1 files changed, 4 insertions, 4 deletions
| @@ -35,7 +35,7 @@ It will make a GET request to `https://example.com/.well-known/nostr.json?name=b | |||
| 35 | } | 35 | } |
| 36 | ```` | 36 | ```` |
| 37 | 37 | ||
| 38 | or with the **optional** `"relays"` and/or `"account_uris"` attributes: | 38 | or with the **optional** `"relays"` and/or `"account_paths"` attributes: |
| 39 | 39 | ||
| 40 | ```json | 40 | ```json |
| 41 | { | 41 | { |
| @@ -45,8 +45,8 @@ or with the **optional** `"relays"` and/or `"account_uris"` attributes: | |||
| 45 | "relays": { | 45 | "relays": { |
| 46 | "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9": [ "wss://relay.example.com", "wss://relay2.example.com" ] | 46 | "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9": [ "wss://relay.example.com", "wss://relay2.example.com" ] |
| 47 | }, | 47 | }, |
| 48 | "account_uris": { | 48 | "account_paths": { |
| 49 | "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9": "https://bob.com/profile/bob" | 49 | "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9": "/profile/bob" |
| 50 | } | 50 | } |
| 51 | } | 51 | } |
| 52 | ```` | 52 | ```` |
| @@ -55,7 +55,7 @@ If the pubkey matches the one given in `"names"` (as in the example above) that | |||
| 55 | 55 | ||
| 56 | The optional `"relays"` attribute may contain an object with public keys as properties and arrays of relay URLs as values. When present, that can be used to help clients learn in which relays that user may be found. Web servers which serve `/.well-known/nostr.json` files dynamically based on the query string SHOULD also serve the relays data for any name they serve in the same reply when that is available. | 56 | The optional `"relays"` attribute may contain an object with public keys as properties and arrays of relay URLs as values. When present, that can be used to help clients learn in which relays that user may be found. Web servers which serve `/.well-known/nostr.json` files dynamically based on the query string SHOULD also serve the relays data for any name they serve in the same reply when that is available. |
| 57 | 57 | ||
| 58 | The optional `"account_uris"` attribute may contain an object with public keys as properties and URIs as values. When present, this allows clients to direct their users to a URI which provides more information about the account on the server which was used to validate the given public key. Clients should ignore any URIs which don't include the server's `<domain>`. | 58 | The optional `"account_paths"` attribute may contain an object with public keys as properties and URIs as values. When present, this allows clients to direct their users to a URI that provides more information about the account on the same NIP-05 server -- for example, if the address is `"bob@example.com"` and the account_path for Bob's public key is `"/profile/bob"` the client may have a link to `https://example.com/profile/bob` at Bob's NIP-05 address. |
| 59 | 59 | ||
| 60 | ## Finding users from their NIP-05 identifier | 60 | ## Finding users from their NIP-05 identifier |
| 61 | 61 | ||