| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-03-20 | remove mentions to note1 codes. | fiatjaf | |
| 2025-08-11 | NIP-21: Fix markup issue by closing backtick (#2008) | Yoji Shidara | |
| 2025-05-24 | Associating HTML documents to Nostr entities with `<link>` (#1897) | fiatjaf_ | |
| Co-authored-by: hodlbod <jstaab@protonmail.com> Co-authored-by: Râu Cao <842+raucao@users.noreply.github.com> | |||
| 2024-07-28 | 21.md:use relative link | randymcmillan | |
| 2023-11-16 | remove all NIP authors. | fiatjaf | |
| 2023-05-01 | Change NIP-21 URL->URI | mplorentz | |
| 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-04-17 | Update 21.md | Martin Dutra | |
| Add link to NIP-19 | |||
| 2023-01-25 | add NIP-21, `nostr:` url scheme. | fiatjaf | |