nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity
f44c5e8141
nips/21.md

32 lines
1.4 KiB
Markdown
Raw Normal View History

add NIP-21, `nostr:` url scheme.
2023-01-24 08:23:00 -05:00
NIP-21
======
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.
2023-05-01 14:15:06 -04:00
`nostr:` URI scheme
add NIP-21, `nostr:` url scheme.
2023-01-24 08:23:00 -05:00
-------------------
remove all NIP authors.
2023-11-15 19:42:51 -05:00
`draft` `optional`
add NIP-21, `nostr:` url scheme.
2023-01-24 08:23:00 -05:00
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.
2023-05-01 14:15:06 -04:00
This NIP standardizes the usage of a common URI scheme for maximum interoperability and openness in the network.
add NIP-21, `nostr:` url scheme.
2023-01-24 08:23:00 -05:00
The scheme is `nostr:`.
21.md:use relative link
2024-07-28 15:36:31 -04:00
The identifiers that come after are expected to be the same as those defined in [NIP-19](19.md) (except `nsec`).
add NIP-21, `nostr:` url scheme.
2023-01-24 08:23:00 -05:00
## Examples
- `nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9`
- `nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpp4mhxue69uhhytnc9e3k7mgpz4mhxue69uhkg6nzv9ejuumpv34kytnrdaksjlyr9p`
- `nostr:note1fntxtkcy9pjwucqwa9mddn7v03wwwsu9j330jj350nvhpky2tuaspk6nqc`
- `nostr:nevent1qqstna2yrezu5wghjvswqqculvvwxsrcvu7uc0f78gan4xqhvz49d9spr3mhxue69uhkummnw3ez6un9d3shjtn4de6x2argwghx6egpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5nxnepm`
Adds typed schemes.
2024-10-15 12:34:17 -04:00
# Typed Schemes
Nostr apps SHOULD register for the specific event types they support, enabling operating systems to suggest only applications that can handle those event types and allowing the OS to have a different default application for each type.
modifies scheme to nostr+
2024-10-15 15:12:42 -04:00
The typed scheme is `nostr+<event type number>:` followed by a `note`, `nevent` or an `naddr` [NIP-19](19.md) identifier.
Adds typed schemes.
2024-10-15 12:34:17 -04:00
## Examples
modifies scheme to nostr+
2024-10-15 15:12:42 -04:00
- `nostr+1:note1fntxtkcy9pjwucqwa9mddn7v03wwwsu9j330jj350nvhpky2tuaspk6nqc`
- `nostr+1:nevent1qqstna2yrezu5wghjvswqqculvvwxsrcvu7uc0f78gan4xqhvz49d9spr3mhxue69uhkummnw3ez6un9d3shjtn4de6x2argwghx6egpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5nxnepm`
Reference in New Issue Copy Permalink