Commit Graph

6 Commits

Author SHA1 Message Date
Mariano Pérez Rodríguez
cd97ce5a72
Merge remote-tracking branch 'origin/master' into markdownlint
# By Jonathan Staab (1) and mplorentz (1)
# Via fiatjaf_
* origin/master:
  Change NIP-21 URL->URI
  Add dim tag to NIP 94

# Conflicts:
#	21.md
2023-05-01 17:22:06 -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
Mariano Pérez Rodríguez
e8415d5bf7
Merge remote-tracking branch 'origin/master' into markdownlint
# By Asai Toshiya (1) and Martin Dutra (1)
# Via GitHub
* origin/master:
  Update 08.md
  Update 21.md

# Conflicts:
#	08.md
2023-04-19 12:01:53 -03:00
Martin Dutra
e1cda356a0 Update 21.md
Add link to NIP-19
2023-04-17 17:53:42 -03:00
Mariano Pérez Rodríguez
ae3fdaf5ed
Apply minimal-ish changes to fit configuration 2023-04-17 13:31:18 -03:00
fiatjaf
45649d7b4d add NIP-21, nostr: url scheme. 2023-01-25 13:08:20 -03:00