From 0ca9be82247d9c1f93ac4319042d2364b7d18b30 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Thu, 29 Dec 2022 21:02:32 -0300 Subject: clarify nip19 purpose. --- 05.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to '05.md') diff --git a/05.md b/05.md index fdf1101..b489b4b 100644 --- a/05.md +++ b/05.md @@ -47,9 +47,9 @@ A client may implement support for finding users' public keys from _internet ide 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). -### Public keys must be in Hex format +### Public keys must be in hex format -Keys must be returned in Hex format. Keys returned in npub format are not supported by this spec. +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. ### User Discovery implementation suggestion @@ -78,7 +78,6 @@ Users should ensure that their `/.well-known/nostr.json` is served with the HTTP ### Security Constraints -The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects. +The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects. Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` endpoint. - -- cgit v1.2.3