Why Nostr? What is Njump?
2024-06-10 20:01:57

npub165…63l5r on Nostr: commit e5f29868abf90ecfc0d18f72dac6f286cb81032b Author: randymcmillan ...

commit e5f29868abf90ecfc0d18f72dac6f286cb81032b
Author: randymcmillan <[email protected]>
Date: Wed May 22 18:10:37 2024 -0400

docs

diff --git a/docs/35.md.css.html b/docs/35.md.css.html
new file mode 100644
index 0000000..32c7996
--- /dev/null
+++ b/docs/35.md.css.html
@@ -0,0 +1,254 @@
+<!DOCTYPE html>
+<html xmlns="http://www.w3.org/1999/xhtml"; lang="" xml:lang="">
+<head>
+ <meta charset="utf-8" />
+ <meta name="generator" content="pandoc" />
+ <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
+ <title>35</title>
+ <style>
+ html {
+ color: #1a1a1a;
+ background-color: #fdfdfd;
+ }
+ body {
+ margin: 0 auto;
+ max-width: 36em;
+ padding-left: 50px;
+ padding-right: 50px;
+ padding-top: 50px;
+ padding-bottom: 50px;
+ hyphens: auto;
+ overflow-wrap: break-word;
+ text-rendering: optimizeLegibility;
+ font-kerning: normal;
+ }
+ @media (max-width: 600px) {
+ body {
+ font-size: 0.9em;
+ padding: 12px;
+ }
+ h1 {
+ font-size: 1.8em;
+ }
+ }
+ @media print {
+ html {
+ background-color: white;
+ }
+ body {
+ background-color: transparent;
+ color: black;
+ font-size: 12pt;
+ }
+ p, h2, h3 {
+ orphans: 3;
+ widows: 3;
+ }
+ h2, h3, h4 {
+ page-break-after: avoid;
+ }
+ }
+ p {
+ margin: 1em 0;
+ }
+ a {
+ color: #1a1a1a;
+ }
+ a:visited {
+ color: #1a1a1a;
+ }
+ img {
+ max-width: 100%;
+ }
+ svg {
+ height: auto;
+ max-width: 100%;
+ }
+ h1, h2, h3, h4, h5, h6 {
+ margin-top: 1.4em;
+ }
+ h5, h6 {
+ font-size: 1em;
+ font-style: italic;
+ }
+ h6 {
+ font-weight: normal;
+ }
+ ol, ul {
+ padding-left: 1.7em;
+ margin-top: 1em;
+ }
+ li > ol, li > ul {
+ margin-top: 0;
+ }
+ blockquote {
+ margin: 1em 0 1em 1.7em;
+ padding-left: 1em;
+ border-left: 2px solid #e6e6e6;
+ color: #606060;
+ }
+ code {
+ font-family: Menlo, Monaco, Consolas, 'Lucida Console', monospace;
+ font-size: 85%;
+ margin: 0;
+ hyphens: manual;
+ }
+ pre {
+ margin: 1em 0;
+ overflow: auto;
+ }
+ pre code {
+ padding: 0;
+ overflow: visible;
+ overflow-wrap: normal;
+ }
+ .sourceCode {
+ background-color: transparent;
+ overflow: visible;
+ }
+ hr {
+ background-color: #1a1a1a;
+ border: none;
+ height: 1px;
+ margin: 1em 0;
+ }
+ table {
+ margin: 1em 0;
+ border-collapse: collapse;
+ width: 100%;
+ overflow-x: auto;
+ display: block;
+ font-variant-numeric: lining-nums tabular-nums;
+ }
+ table caption {
+ margin-bottom: 0.75em;
+ }
+ tbody {
+ margin-top: 0.5em;
+ border-top: 1px solid #1a1a1a;
+ border-bottom: 1px solid #1a1a1a;
+ }
+ th {
+ border-top: 1px solid #1a1a1a;
+ padding: 0.25em 0.5em 0.25em 0.5em;
+ }
+ td {
+ padding: 0.125em 0.5em 0.25em 0.5em;
+ }
+ header {
+ margin-bottom: 4em;
+ text-align: center;
+ }
+ #TOC li {
+ list-style: none;
+ }
+ #TOC ul {
+ padding-left: 1.3em;
+ }
+ #TOC > ul {
+ padding-left: 0;
+ }
+ #TOC a:not(:hover) {
+ text-decoration: none;
+ }
+ code{white-space: pre-wrap;}
+ span.smallcaps{font-variant: small-caps;}
+ div.columns{display: flex; gap: min(4vw, 1.5em);}
+ div.column{flex: auto; overflow-x: auto;}
+ div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
+ /* The extra [class] is a hack that increases specificity enough to
+ override a similar rule in reveal.js */
+ ul.task-list[class]{list-style: none;}
+ ul.task-list li input[type="checkbox"] {
+ font-size: inherit;
+ width: 0.8em;
+ margin: 0 0.8em 0.2em -1.6em;
+ vertical-align: middle;
+ }
+ .display.math{display: block; text-align: center; margin: 0.5rem auto;}
+ </style>
+</head>
+<body>
+<h1 id="nip-35">NIP-35</h1>
+<h2 id="torrents">Torrents</h2>
+<p><code>draft</code> <code>optional</code></p>
+<p>This NIP defined a new <code>kind 2003</code> which is a Torrent.</p>
+<p><code>kind 2003</code> is a simple torrent index where there is
+enough information to search for content and construct the magnet link.
+No torrent files exist on nostr.</p>
+<h2 id="tags">Tags</h2>
+<ul>
+<li><code>x</code>: V1 BitTorrent Info Hash, as seen in the <a
+href="https://www.bittorrent.org/beps/bep_0053.html">magnet link</a>
+<code>magnet:?xt=urn:btih:HASH</code></li>
+<li><code>file</code>: A file entry inside the torrent, including the
+full path ie. <code>info/example.txt</code></li>
+<li><code>tracker</code>: (Optional) A tracker to use for this
+torrent</li>
+</ul>
+<p>In order to make torrents searchable by general category, you SHOULD
+include a few tags like <code>movie</code>, <code>tv</code>,
+<code>HD</code>, <code>UHD</code> etc.</p>
+<h2 id="tag-prefixes">Tag prefixes</h2>
+<p>Tag prefixes are used to label the content with references, ie.
+<code>["i", ".md.css.htmlb:1234"]</code></p>
+<ul>
+<li><code>tcat</code>: A comma separated text category path, ie.
+<code>["i", "tcat:video,movie,4k"]</code>, this should also match the
+<code>newznab</code> category in a best effort approach.</li>
+<li><code>newznab</code>: The category ID from <a
+href="https://github.com/Prowlarr/Prowlarr/blob/develop/src/NzbDrone.Core/Indexers/NewznabStandardCategory.cs">newznab</a></li>;
+<li><code>.md.css.htmlb</code>: <a href="https://www.themoviedb.org/">The movie
+database</a> id.</li>
+<li><code>ttvdb</code>: <a href="https://thetvdb.com/">TV database</a>
+id.</li>
+<li><code>.md.css.htmlb</code>: <a href="https://www..md.css.htmlb.com/">IMDB</a>; id.</li>
+<li><code>mal</code>: <a href="https://myanimelist.net/">MyAnimeList</a>;
+id.</li>
+<li><code>anilist</code>: <a href="https://anilist.co/">AniList</a>;
+id.</li>
+</ul>
+<p>A second level prefix should be included where the database supports
+multiple media types. - <code>.md.css.htmlb:movie:693134</code> maps to
+<code>themoviedb.org/movie/693134</code> -
+<code>ttvdb:movie:290272</code> maps to
+<code>thetvdb.com/movies/dune-part-two</code> -
+<code>mal:anime:9253</code> maps to
+<code>myanimelist.net/anime/9253</code> - <code>mal:manga:17517</code>
+maps to <code>myanimelist.net/manga/17517</code></p>
+<p>In some cases the url mapping isnt direct, mapping the url in general
+is out of scope for this NIP, the section above is only a guide so that
+implementers have enough information to succsesfully map the url if they
+wish.</p>
+<pre class="jsonc"><code>{
+ &quot;kind&quot;: 2003,
+ &quot;content&quot;: &quot;&lt;long-description-pre-formatted&gt;&quot;,
+ &quot;tags&quot;: [
+ [&quot;title&quot;, &quot;&lt;torrent-title&gt;&quot;],
+ [&quot;x&quot;, &quot;&lt;bittorrent-info-hash&gt;&quot;],
+ [&quot;file&quot;, &quot;&lt;file-name&gt;&quot;, &quot;&lt;file-size-in-bytes&gt;&quot;],
+ [&quot;file&quot;, &quot;&lt;file-name&gt;&quot;, &quot;&lt;file-size-in-bytes&gt;&quot;],
+ [&quot;tracker&quot;, &quot;udp://mytacker.com:1337&quot;],
+ [&quot;tracker&quot;, &quot;http://1337-tracker.net/announce&quot;],
+ [&quot;i&quot;, &quot;tcat:video,movie,4k&quot;],
+ [&quot;i&quot;, &quot;newznab:2045&quot;],
+ [&quot;i&quot;, &quot;.md.css.htmlb:tt15239678&quot;],
+ [&quot;i&quot;, &quot;.md.css.htmlb:movie:693134&quot;],
+ [&quot;i&quot;, &quot;ttvdb:movie:290272&quot;],
+ [&quot;t&quot;, &quot;movie&quot;],
+ [&quot;t&quot;, &quot;4k&quot;],
+ ]
+}</code></pre>
+<h2 id="torrent-comments">Torrent Comments</h2>
+<p>A torrent comment is a <code>kind 2004</code> event which is used to
+reply to a torrent event.</p>
+<p>This event works exactly like a <code>kind 1</code> and should follow
+<code>NIP-10</code> for tagging.</p>
+<h2 id="implementations">Implementations</h2>
+<ol type="1">
+<li><a href="https://git.v0l.io/Kieran/dtan">dtan.xyz</a></li>;
+<li><a
+href="https://github.com/hzrd149/nostrudel/tree/next/src/views/torrents">nostrudel.ninja</a></li>;
+</ol>
+</body>
+</html>
diff --git a/docs/35.md.html b/docs/35.md.html
new file mode 100644
index 0000000..a0dad53
--- /dev/null
+++ b/docs/35.md.html
@@ -0,0 +1,81 @@
+<h1 id="nip-35">NIP-35</h1>
+<h2 id="torrents">Torrents</h2>
+<p><code>draft</code> <code>optional</code></p>
+<p>This NIP defined a new <code>kind 2003</code> which is a Torrent.</p>
+<p><code>kind 2003</code> is a simple torrent index where there is
+enough information to search for content and construct the magnet link.
+No torrent files exist on nostr.</p>
+<h2 id="tags">Tags</h2>
+<ul>
+<li><code>x</code>: V1 BitTorrent Info Hash, as seen in the <a
+href="https://www.bittorrent.org/beps/bep_0053.html">magnet link</a>
+<code>magnet:?xt=urn:btih:HASH</code></li>
+<li><code>file</code>: A file entry inside the torrent, including the
+full path ie. <code>info/example.txt</code></li>
+<li><code>tracker</code>: (Optional) A tracker to use for this
+torrent</li>
+</ul>
+<p>In order to make torrents searchable by general category, you SHOULD
+include a few tags like <code>movie</code>, <code>tv</code>,
+<code>HD</code>, <code>UHD</code> etc.</p>
+<h2 id="tag-prefixes">Tag prefixes</h2>
+<p>Tag prefixes are used to label the content with references, ie.
+<code>["i", ".md.htmlb:1234"]</code></p>
+<ul>
+<li><code>tcat</code>: A comma separated text category path, ie.
+<code>["i", "tcat:video,movie,4k"]</code>, this should also match the
+<code>newznab</code> category in a best effort approach.</li>
+<li><code>newznab</code>: The category ID from <a
+href="https://github.com/Prowlarr/Prowlarr/blob/develop/src/NzbDrone.Core/Indexers/NewznabStandardCategory.cs">newznab</a></li>;
+<li><code>.md.htmlb</code>: <a href="https://www.themoviedb.org/">The movie
+database</a> id.</li>
+<li><code>ttvdb</code>: <a href="https://thetvdb.com/">TV database</a>
+id.</li>
+<li><code>.md.htmlb</code>: <a href="https://www..md.htmlb.com/">IMDB</a>; id.</li>
+<li><code>mal</code>: <a href="https://myanimelist.net/">MyAnimeList</a>;
+id.</li>
+<li><code>anilist</code>: <a href="https://anilist.co/">AniList</a>;
+id.</li>
+</ul>
+<p>A second level prefix should be included where the database supports
+multiple media types. - <code>.md.htmlb:movie:693134</code> maps to
+<code>themoviedb.org/movie/693134</code> -
+<code>ttvdb:movie:290272</code> maps to
+<code>thetvdb.com/movies/dune-part-two</code> -
+<code>mal:anime:9253</code> maps to
+<code>myanimelist.net/anime/9253</code> - <code>mal:manga:17517</code>
+maps to <code>myanimelist.net/manga/17517</code></p>
+<p>In some cases the url mapping isnt direct, mapping the url in general
+is out of scope for this NIP, the section above is only a guide so that
+implementers have enough information to succsesfully map the url if they
+wish.</p>
+<pre class="jsonc"><code>{
+ &quot;kind&quot;: 2003,
+ &quot;content&quot;: &quot;&lt;long-description-pre-formatted&gt;&quot;,
+ &quot;tags&quot;: [
+ [&quot;title&quot;, &quot;&lt;torrent-title&gt;&quot;],
+ [&quot;x&quot;, &quot;&lt;bittorrent-info-hash&gt;&quot;],
+ [&quot;file&quot;, &quot;&lt;file-name&gt;&quot;, &quot;&lt;file-size-in-bytes&gt;&quot;],
+ [&quot;file&quot;, &quot;&lt;file-name&gt;&quot;, &quot;&lt;file-size-in-bytes&gt;&quot;],
+ [&quot;tracker&quot;, &quot;udp://mytacker.com:1337&quot;],
+ [&quot;tracker&quot;, &quot;http://1337-tracker.net/announce&quot;],
+ [&quot;i&quot;, &quot;tcat:video,movie,4k&quot;],
+ [&quot;i&quot;, &quot;newznab:2045&quot;],
+ [&quot;i&quot;, &quot;.md.htmlb:tt15239678&quot;],
+ [&quot;i&quot;, &quot;.md.htmlb:movie:693134&quot;],
+ [&quot;i&quot;, &quot;ttvdb:movie:290272&quot;],
+ [&quot;t&quot;, &quot;movie&quot;],
+ [&quot;t&quot;, &quot;4k&quot;],
+ ]
+}</code></pre>
+<h2 id="torrent-comments">Torrent Comments</h2>
+<p>A torrent comment is a <code>kind 2004</code> event which is used to
+reply to a torrent event.</p>
+<p>This event works exactly like a <code>kind 1</code> and should follow
+<code>NIP-10</code> for tagging.</p>
+<h2 id="implementations">Implementations</h2>
+<ol type="1">
+<li><a href="https://git.v0l.io/Kieran/dtan">dtan.xyz</a></li>;
+<li><a
+href="https://github.com/hzrd149/nostrudel/tree/next/src/views/torrents">nostrudel.ninja</a></li>;
+</ol>
diff --git a/docs/35.md.txt b/docs/35.md.txt
new file mode 100644
index 0000000..7f1dba6
--- /dev/null
+++ b/docs/35.md.txt
@@ -0,0 +1,82 @@
+NIP-35
+
+Torrents
+
+draft optional
+
+This NIP defined a new kind 2003 which is a Torrent.
+
+kind 2003 is a simple torrent index where there is enough information to
+search for content and construct the magnet link. No torrent files exist
+on nostr.
+
+Tags
+
+- x: V1 BitTorrent Info Hash, as seen in the magnet link
+ magnet:?xt=urn:btih:HASH
+- file: A file entry inside the torrent, including the full path ie.
+ info/example.txt
+- tracker: (Optional) A tracker to use for this torrent
+
+In order to make torrents searchable by general category, you SHOULD
+include a few tags like movie, tv, HD, UHD etc.
+
+Tag prefixes
+
+Tag prefixes are used to label the content with references, ie.
+["i", ".txtb:1234"]
+
+- tcat: A comma separated text category path, ie.
+ ["i", "tcat:video,movie,4k"], this should also match the newznab
+ category in a best effort approach.
+- newznab: The category ID from newznab
+- .txtb: The movie database id.
+- ttvdb: TV database id.
+- .txtb: IMDB id.
+- mal: MyAnimeList id.
+- anilist: AniList id.
+
+A second level prefix should be included where the database supports
+multiple media types. - .txtb:movie:693134 maps to
+themoviedb.org/movie/693134 - ttvdb:movie:290272 maps to
+thetvdb.com/movies/dune-part-two - mal:anime:9253 maps to
+myanimelist.net/anime/9253 - mal:manga:17517 maps to
+myanimelist.net/manga/17517
+
+In some cases the url mapping isnt direct, mapping the url in general is
+out of scope for this NIP, the section above is only a guide so that
+implementers have enough information to succsesfully map the url if they
+wish.
+
+ {
+ "kind": 2003,
+ "content": "<long-description-pre-formatted>",
+ "tags": [
+ ["title", "<torrent-title>"],
+ ["x", "<bittorrent-info-hash>"],
+ ["file", "<file-name>", "<file-size-in-bytes>"],
+ ["file", "<file-name>", "<file-size-in-bytes>"],
+ ["tracker", "udp://mytacker.com:1337"],
+ ["tracker", "http://1337-tracker.net/announce";],
+ ["i", "tcat:video,movie,4k"],
+ ["i", "newznab:2045"],
+ ["i", ".txtb:tt15239678"],
+ ["i", ".txtb:movie:693134"],
+ ["i", "ttvdb:movie:290272"],
+ ["t", "movie"],
+ ["t", "4k"],
+ ]
+ }
+
+Torrent Comments
+
+A torrent comment is a kind 2004 event which is used to reply to a
+torrent event.
+
+This event works exactly like a kind 1 and should follow NIP-10 for
+tagging.
+
+Implementations
+
+1. dtan.xyz
+2. nostrudel.ninja
diff --git a/docs/README.md.css.html b/docs/README.md.css.html
index 7abd966..29ee0c9 100644
--- a/docs/README.md.css.html
+++ b/docs/README.md.css.html
@@ -236,6 +236,7 @@ marketplaces)</a></li>
<li><a href="31.md.css.html">NIP-31: Dealing with Unknown Events</a></li>
<li><a href="32.md.css.html">NIP-32: Labeling</a></li>
<li><a href="34.md.css.html">NIP-34: <code>git</code> stuff</a></li>
+<li><a href="35.md.css.html">NIP-35: Torrents</a></li>
<li><a href="36.md.css.html">NIP-36: Sensitive Content</a></li>
<li><a href="38.md.css.html">NIP-38: User Statuses</a></li>
<li><a href="39.md.css.html">NIP-39: External Identities in Profiles</a></li>
@@ -462,6 +463,16 @@ href="https://github.com/nostrocket/NIPS/blob/main/Problems.md.css.html">nostroc
<td><a href="32.md.css.html">32</a></td>
</tr>
<tr class="even">
+<td><code>2003</code></td>
+<td>Torrent</td>
+<td><a href="35.md.css.html">35</a></td>
+</tr>
+<tr class="odd">
+<td><code>2004</code></td>
+<td>Torrent Comment</td>
+<td><a href="35.md.css.html">35</a></td>
+</tr>
+<tr class="even">
<td><code>4550</code></td>
<td>Community Post Approval</td>
<td><a href="72.md.css.html">72</a></td>
@@ -887,12 +898,12 @@ href="https://github.com/shocknet/Lightning.Pub/blob/master/proto/autogenerated/
<p>Please update these lists when proposing NIPs introducing new event
kinds.</p>
<h2 id="standardized-tags">Standardized Tags</h2>
-<table>
+<table style="width:100%;">
<colgroup>
-<col style="width: 15%" />
-<col style="width: 32%" />
-<col style="width: 18%" />
-<col style="width: 33%" />
+<col style="width: 14%" />
+<col style="width: 29%" />
+<col style="width: 25%" />
+<col style="width: 30%" />
</colgroup>
<thead>
<tr class="header">
@@ -906,7 +917,7 @@ kinds.</p>
<tr class="odd">
<td><code>e</code></td>
<td>event id (hex)</td>
-<td>relay URL, marker</td>
+<td>relay URL, marker, pubkey (hex)</td>
<td><a href="01.md.css.html">01</a>, <a href="10.md.css.html">10</a></td>
</tr>
<tr class="even">
diff --git a/docs/README.md.html b/docs/README.md.html
index 5b95ee5..5267fb7 100644
--- a/docs/README.md.html
+++ b/docs/README.md.html
@@ -65,6 +65,7 @@ marketplaces)</a></li>
<li><a href="31.md.html">NIP-31: Dealing with Unknown Events</a></li>
<li><a href="32.md.html">NIP-32: Labeling</a></li>
<li><a href="34.md.html">NIP-34: <code>git</code> stuff</a></li>
+<li><a href="35.md.html">NIP-35: Torrents</a></li>
<li><a href="36.md.html">NIP-36: Sensitive Content</a></li>
<li><a href="38.md.html">NIP-38: User Statuses</a></li>
<li><a href="39.md.html">NIP-39: External Identities in Profiles</a></li>
@@ -291,6 +292,16 @@ href="https://github.com/nostrocket/NIPS/blob/main/Problems.md.html">nostrocket<;
<td><a href="32.md.html">32</a></td>
</tr>
<tr class="even">
+<td><code>2003</code></td>
+<td>Torrent</td>
+<td><a href="35.md.html">35</a></td>
+</tr>
+<tr class="odd">
+<td><code>2004</code></td>
+<td>Torrent Comment</td>
+<td><a href="35.md.html">35</a></td>
+</tr>
+<tr class="even">
<td><code>4550</code></td>
<td>Community Post Approval</td>
<td><a href="72.md.html">72</a></td>
@@ -716,12 +727,12 @@ href="https://github.com/shocknet/Lightning.Pub/blob/master/proto/autogenerated/
<p>Please update these lists when proposing NIPs introducing new event
kinds.</p>
<h2 id="standardized-tags">Standardized Tags</h2>
-<table>
+<table style="width:100%;">
<colgroup>
-<col style="width: 15%" />
-<col style="width: 32%" />
-<col style="width: 18%" />
-<col style="width: 33%" />
+<col style="width: 14%" />
+<col style="width: 29%" />
+<col style="width: 25%" />
+<col style="width: 30%" />
</colgroup>
<thead>
<tr class="header">
@@ -735,7 +746,7 @@ kinds.</p>
<tr class="odd">
<td><code>e</code></td>
<td>event id (hex)</td>
-<td>relay URL, marker</td>
+<td>relay URL, marker, pubkey (hex)</td>
<td><a href="01.md.html">01</a>, <a href="10.md.html">10</a></td>
</tr>
<tr class="even">
diff --git a/docs/README.md.txt b/docs/README.md.txt
index 8763291..b8a2dad 100644
--- a/docs/README.md.txt
+++ b/docs/README.md.txt
@@ -55,6 +55,7 @@ List
- NIP-31: Dealing with Unknown Events
- NIP-32: Labeling
- NIP-34: git stuff
+- NIP-35: Torrents
- NIP-36: Sensitive Content
- NIP-38: User Statuses
- NIP-39: External Identities in Profiles
@@ -164,6 +165,10 @@ Event Kinds

1985 Label 32

+ 2003 Torrent 35
+
+ 2004 Torrent Comment 35
+
4550 Community Post Approval 72

5000-5999 Job Request 90
@@ -340,109 +345,115 @@ kinds.

Standardized Tags

- -------------------------------------------------------------------------------
- name value other NIP
- parameters
- ----------------- ----------------------- ------------- -----------------------
- e event id (hex) relay URL, 01, 10
- marker
+ --------------------------------------------------------------------------------
+ name value other parameters NIP
+ ----------------- --------------------- ------------------ ---------------------
+ e event id (hex) relay URL, marker, 01, 10
+ pubkey (hex)

- p pubkey (hex) relay URL, 01, 02
- petname
+ p pubkey (hex) relay URL, petname 01, 02

- a coordinates to an event relay URL 01
+ a coordinates to an relay URL 01
+ event

- d identifier &ndash; 01
+ d identifier &ndash; 01

- g geohash &ndash; 52
+ g geohash &ndash; 52

- i identity proof 39
+ i identity proof 39

- k kind number (string) &ndash; 18, 25, 72
+ k kind number (string) &ndash; 18, 25, 72

- l label, label namespace annotations 32
+ l label, label annotations 32
+ namespace

- L label namespace &ndash; 32
+ L label namespace &ndash; 32

- m MIME type &ndash; 94
+ m MIME type &ndash; 94

- q event id (hex) relay URL 18
+ q event id (hex) relay URL 18

- r a reference (URL, etc) petname
+ r a reference (URL, petname
+ etc)

- r relay url marker 65
+ r relay url marker 65

- t hashtag &ndash;
+ t hashtag &ndash;

- alt summary &ndash; 31
+ alt summary &ndash; 31

- amount millisatoshis, &ndash; 57
- stringified
+ amount millisatoshis, &ndash; 57
+ stringified

- bolt11 bolt11 invoice &ndash; 57
+ bolt11 bolt11 invoice &ndash; 57

- challenge challenge string &ndash; 42
+ challenge challenge string &ndash; 42

- client name, address relay URL 89
+ client name, address relay URL 89

- clone git clone URL &ndash; 34
+ clone git clone URL &ndash; 34

- content-warning reason &ndash; 36
+ content-warning reason &ndash; 36

- delegation pubkey, conditions, &ndash; 26
- delegation token
+ delegation pubkey, conditions, &ndash; 26
+ delegation token

- description description &ndash; 34, 57, 58
+ description description &ndash; 34, 57, 58

- emoji shortcode, image URL &ndash; 30
+ emoji shortcode, image URL &ndash; 30

- encrypted &ndash; &ndash; 90
+ encrypted &ndash; &ndash; 90

- expiration unix timestamp (string) &ndash; 40
+ expiration unix timestamp &ndash; 40
+ (string)

- goal event id (hex) relay URL 75
+ goal event id (hex) relay URL 75

- image image URL dimensions in 23, 58
- pixels
+ image image URL dimensions in 23, 58
+ pixels

- imeta inline metadata &ndash; 92
+ imeta inline metadata &ndash; 92

- lnurl bech32 encoded lnurl &ndash; 57
+ lnurl bech32 encoded lnurl &ndash; 57

- location location string &ndash; 52, 99
+ location location string &ndash; 52, 99

- name name &ndash; 34, 58
+ name name &ndash; 34, 58

- nonce random &ndash; 13
+ nonce random &ndash; 13

- preimage hash of bolt11 invoice &ndash; 57
+ preimage hash of bolt11 &ndash; 57
+ invoice

- price price currency, 99
- frequency
+ price price currency, 99
+ frequency

- proxy external ID protocol 48
+ proxy external ID protocol 48

- published_at unix timestamp (string) &ndash; 23
+ published_at unix timestamp &ndash; 23
+ (string)

- relay relay url &ndash; 42, 17
+ relay relay url &ndash; 42, 17

- relays relay list &ndash; 57
+ relays relay list &ndash; 57

- server file storage server url &ndash; 96
+ server file storage server &ndash; 96
+ url

- subject subject &ndash; 14, 17
+ subject subject &ndash; 14, 17

- summary article summary &ndash; 23
+ summary article summary &ndash; 23

- thumb badge thumbnail dimensions in 58
- pixels
+ thumb badge thumbnail dimensions in 58
+ pixels

- title article title &ndash; 23
+ title article title &ndash; 23

- web webpage URL &ndash; 34
+ web webpage URL &ndash; 34

- zap pubkey (hex), relay URL weight 57
- -------------------------------------------------------------------------------
+ zap pubkey (hex), relay weight 57
+ URL
+ --------------------------------------------------------------------------------

Criteria for acceptance of NIPs
Author Public Key
npub165znf6zagwkwhdmsq86r0wymgl8f3wrcn5pnssn0sycc5nkypl2sr63l5r