diff options
| author | Vitor Pamplona <vitor@vitorpamplona.com> | 2024-05-30 15:32:46 -0400 |
|---|---|---|
| committer | Vitor Pamplona <vitor@vitorpamplona.com> | 2024-05-30 15:32:46 -0400 |
| commit | d5b77b6d7348061cd0f16adc35e4d02a3a0b7380 (patch) | |
| tree | f00539ec0e0a8b6bf027ff6a9b93846adafa02b3 /05.md | |
| parent | 48674e563865b1cb7bb3c5c7869d20055446f408 (diff) | |
| parent | 5c796c19fd6330628a0b328bfcf5270cb2bc3aff (diff) | |
Merge remote-tracking branch 'upstream/master' into draft-event
# Conflicts:
# README.md
Diffstat (limited to '05.md')
| -rw-r--r-- | 05.md | 4 |
1 files changed, 2 insertions, 2 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"` attribute: | 38 | or with the **recommended** `"relays"` attribute: |
| 39 | 39 | ||
| 40 | ```json | 40 | ```json |
| 41 | { | 41 | { |
| @@ -50,7 +50,7 @@ or with the **optional** `"relays"` attribute: | |||
| 50 | 50 | ||
| 51 | If the pubkey matches the one given in `"names"` (as in the example above) that means the association is right and the `"nip05"` identifier is valid and can be displayed. | 51 | If the pubkey matches the one given in `"names"` (as in the example above) that means the association is right and the `"nip05"` identifier is valid and can be displayed. |
| 52 | 52 | ||
| 53 | 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 the specific 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. | 53 | The recommended `"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 the specific 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. |
| 54 | 54 | ||
| 55 | ## Finding users from their NIP-05 identifier | 55 | ## Finding users from their NIP-05 identifier |
| 56 | 56 | ||