diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2022-12-29 21:02:32 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2022-12-29 21:02:32 -0300 |
| commit | 0ca9be82247d9c1f93ac4319042d2364b7d18b30 (patch) | |
| tree | e0474dc6410e10e953193d0670e30a663263f101 /05.md | |
| parent | a37a27afb905b71c1beda7c5a9ec12938d8b8a87 (diff) | |
clarify nip19 purpose.
Diffstat (limited to '05.md')
| -rw-r--r-- | 05.md | 7 |
1 files changed, 3 insertions, 4 deletions
| @@ -47,9 +47,9 @@ A client may implement support for finding users' public keys from _internet ide | |||
| 47 | 47 | ||
| 48 | For example, if after finding that `bob@bob.com` has the public key `abc...def`, the user clicks a button to follow that profile, the client must keep a primary reference to `abc...def`, not `bob@bob.com`. If, for any reason, the address `https://bob.com/.well-known/nostr.json?name=bob` starts returning the public key `1d2...e3f` at any time in the future, the client must not replace `abc...def` in his list of followed profiles for the user (but it should stop displaying "bob@bob.com" for that user, as that will have become an invalid `"nip05"` property). | 48 | For example, if after finding that `bob@bob.com` has the public key `abc...def`, the user clicks a button to follow that profile, the client must keep a primary reference to `abc...def`, not `bob@bob.com`. If, for any reason, the address `https://bob.com/.well-known/nostr.json?name=bob` starts returning the public key `1d2...e3f` at any time in the future, the client must not replace `abc...def` in his list of followed profiles for the user (but it should stop displaying "bob@bob.com" for that user, as that will have become an invalid `"nip05"` property). |
| 49 | 49 | ||
| 50 | ### Public keys must be in Hex format | 50 | ### Public keys must be in hex format |
| 51 | 51 | ||
| 52 | Keys must be returned in Hex format. Keys returned in npub format are not supported by this spec. | 52 | Keys must be returned in hex format. Keys in NIP-19 `npub` format are are only meant to be used for display in client UIs, not in this NIP. |
| 53 | 53 | ||
| 54 | ### User Discovery implementation suggestion | 54 | ### User Discovery implementation suggestion |
| 55 | 55 | ||
| @@ -78,7 +78,6 @@ Users should ensure that their `/.well-known/nostr.json` is served with the HTTP | |||
| 78 | 78 | ||
| 79 | ### Security Constraints | 79 | ### Security Constraints |
| 80 | 80 | ||
| 81 | The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects. | 81 | The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects. |
| 82 | 82 | ||
| 83 | Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` endpoint. | 83 | Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` endpoint. |
| 84 | |||