diff options
| author | mplorentz <mplorentz@users.noreply.github.com> | 2023-05-01 14:15:06 -0400 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2023-05-01 15:16:30 -0300 |
| commit | 7f75d0db33435fe9fcb6c04f18d0e610b17cebb4 (patch) | |
| tree | 0d35b3b6b416a05426b9177747c1fa1f7c171021 | |
| parent | 346036208ccca6f31313f1e909ff17ea3563fb46 (diff) | |
Change NIP-21 URL->URI
I think the `nostr:...` scheme is not actually a Uniform Resource Locator, because it doesn't tell you where the data is located. For instance if I see the string `nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9` I understand that this identifies a Nostr keypair but I don't know where to find data for that keypair. The scheme does fall under the definition of a Uniform Resource Identifier, or maybe even the stricter class Uniform Resource Name. But nobody talks about URNs, so maybe best to just use the less-specific term "URI" here.
| -rw-r--r-- | 21.md | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -1,12 +1,12 @@ | |||
| 1 | NIP-21 | 1 | NIP-21 |
| 2 | ====== | 2 | ====== |
| 3 | 3 | ||
| 4 | `nostr:` URL scheme | 4 | `nostr:` URI scheme |
| 5 | ------------------- | 5 | ------------------- |
| 6 | 6 | ||
| 7 | `draft` `optional` `author:fiatjaf` | 7 | `draft` `optional` `author:fiatjaf` |
| 8 | 8 | ||
| 9 | This NIP standardizes the usage of a common URL scheme for maximum interoperability and openness in the network. | 9 | This NIP standardizes the usage of a common URI scheme for maximum interoperability and openness in the network. |
| 10 | 10 | ||
| 11 | The scheme is `nostr:`. | 11 | The scheme is `nostr:`. |
| 12 | 12 | ||