Commit Graph

7 Commits

Author SHA1 Message Date
Yoji Shidara 8830525250
NIP-21: Fix markup issue by closing backtick (#2008) 2025-08-11 19:35:36 +09:00
fiatjaf_ 9eb4a33049
Associating HTML documents to Nostr entities with `<link>` (#1897)
Co-authored-by: hodlbod <jstaab@protonmail.com>
Co-authored-by: Râu Cao <842+raucao@users.noreply.github.com>
2025-05-24 10:42:34 -03:00
randymcmillan 0c1dfa9661
21.md:use relative link 2024-07-28 15:37:14 -04:00
fiatjaf 37f6cbb775 remove all NIP authors. 2023-11-16 10:24:53 -03:00
mplorentz 7f75d0db33 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 15:16:30 -03:00
Martin Dutra e1cda356a0 Update 21.md
Add link to NIP-19
2023-04-17 17:53:42 -03:00
fiatjaf 45649d7b4d add NIP-21, `nostr:` url scheme. 2023-01-25 13:08:20 -03:00