<feed xmlns='http://www.w3.org/2005/Atom'>
<title>npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/21.md, branch tagged-replaceable</title>
<subtitle>[no description]</subtitle>
<id>https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/atom?h=tagged-replaceable</id>
<link rel='self' href='https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/atom?h=tagged-replaceable'/>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/'/>
<updated>2023-11-16T13:24:53+00:00</updated>
<entry>
<title>remove all NIP authors.</title>
<updated>2023-11-16T13:24:53+00:00</updated>
<author>
<name>fiatjaf</name>
<email>fiatjaf@gmail.com</email>
</author>
<published>2023-11-16T00:42:51+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/commit/?id=37f6cbb775126b386414220f783ca0f5f85e7614'/>
<id>urn:sha1:37f6cbb775126b386414220f783ca0f5f85e7614</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Change NIP-21 URL-&gt;URI</title>
<updated>2023-05-01T18:16:30+00:00</updated>
<author>
<name>mplorentz</name>
<email>mplorentz@users.noreply.github.com</email>
</author>
<published>2023-05-01T18:15:06+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/commit/?id=7f75d0db33435fe9fcb6c04f18d0e610b17cebb4'/>
<id>urn:sha1:7f75d0db33435fe9fcb6c04f18d0e610b17cebb4</id>
<content type='text'>
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.</content>
</entry>
<entry>
<title>Update 21.md</title>
<updated>2023-04-17T20:53:42+00:00</updated>
<author>
<name>Martin Dutra</name>
<email>martindsq@hotmail.com</email>
</author>
<published>2023-04-17T18:20:25+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/commit/?id=e1cda356a0d441875b9eafbc1e8769bb40648da1'/>
<id>urn:sha1:e1cda356a0d441875b9eafbc1e8769bb40648da1</id>
<content type='text'>
Add link to NIP-19</content>
</entry>
<entry>
<title>add NIP-21, `nostr:` url scheme.</title>
<updated>2023-01-25T16:08:20+00:00</updated>
<author>
<name>fiatjaf</name>
<email>fiatjaf@gmail.com</email>
</author>
<published>2023-01-24T13:23:00+00:00</published>
<link rel='alternate' type='text/html' href='https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/nips/commit/?id=45649d7b4d40fda4b4db8a02d007e6243a1153c9'/>
<id>urn:sha1:45649d7b4d40fda4b4db8a02d007e6243a1153c9</id>
<content type='text'>
</content>
</entry>
</feed>
