diff options
| author | Alex Gleason <alex@alexgleason.me> | 2025-02-18 17:48:49 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-18 17:48:49 -0600 |
| commit | ebe5ec3b38ac81902b33220c13c14e662f238e09 (patch) | |
| tree | f375f7d9b82ecaf09885ef5f6ca8d167c82ca930 | |
| parent | 330de34c7cc8fc6f34e3dec076f20ceb1af94927 (diff) | |
NIP-05: add dynamic server recommendation
| -rw-r--r-- | 05.md | 6 |
1 files changed, 6 insertions, 0 deletions
| @@ -101,3 +101,9 @@ Users should ensure that their `/.well-known/nostr.json` is served with the HTTP | |||
| 101 | The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects. | 101 | The `/.well-known/nostr.json` endpoint MUST NOT return any HTTP redirects. |
| 102 | 102 | ||
| 103 | Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` endpoint. | 103 | Fetchers MUST ignore any HTTP redirects given by the `/.well-known/nostr.json` endpoint. |
| 104 | |||
| 105 | ### Implementing a NIP-05 server | ||
| 106 | |||
| 107 | NIP-05 is designed so that `nostr.json` can be hosted as a static file. But some services may allow users to sign up and be granted a NIP-05. The `nostr.json` is then served dynamically, depending on the `name` query parameter. | ||
| 108 | |||
| 109 | For these servers, the **case** of the localpart should be considered. It is recommended to make the lowercase representation unique in the database, so that two people cannot reserve the same name in different cases (eg `chad` vs `Chad`). Servers may then serve any case variation of the name to the given pubkey, allowing users to freely change the case of their name. However, the server MUST match the case provided by the `name` query parameter. | ||