From 346036208ccca6f31313f1e909ff17ea3563fb46 Mon Sep 17 00:00:00 2001
From: Jonathan Staab <shtaab@gmail.com>
Date: Fri, 28 Apr 2023 10:21:18 -0500
Subject: [PATCH 1/2] Add dim tag to NIP 94

---
 94.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/94.md b/94.md
index d29548e..24dd346 100644
--- a/94.md
+++ b/94.md
@@ -4,7 +4,7 @@ NIP-94
 File Metadata
 -------------
 
-`draft` `optional` `author:frbitten` `author:kieran` `author:lovvtide` `author:fiatjaf`
+`draft` `optional` `author:frbitten` `author:kieran` `author:lovvtide` `author:fiatjaf` `author:staab`
 
 The purpose of this NIP is to allow an organization and classification of shared files. So that relays can filter and organize in any way that is of interest. With that, multiple types of filesharing clients can be created. NIP-94 support is not expected to be implemented by "social" clients that deal with kind:1 notes or by longform clients that deal with kind:30023 articles.
 
@@ -17,6 +17,7 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr
 * `"aes-256-gcm"` (optional)  key and nonce for AES-GCM encryption with tagSize always 128bits
 * `x` containing the SHA-256 hexencoded string of the file.
 * `size` (optional) size of file in bytes
+* `dim` (optional) size of file in pixels in the form `<width>x<height>`
 * `magnet` (optional) URI to magnet file
 * `i` (optional) torrent infohash
 * `blurhash`(optional) the [blurhash](https://github.com/woltapp/blurhash) to show while the file is being loaded by the client
@@ -33,6 +34,7 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr
     ["m", <MIME type>],
     ["x",<Hash SHA-256>],
     ["size", <size of file in bytes>],
+    ["dim", <size of file in pixels>],
     ["magnet",<magnet URI> ],
     ["i",<torrent infohash>],
     ["blurhash", <value>]

From 7f75d0db33435fe9fcb6c04f18d0e610b17cebb4 Mon Sep 17 00:00:00 2001
From: mplorentz <mplorentz@users.noreply.github.com>
Date: Mon, 1 May 2023 14:15:06 -0400
Subject: [PATCH 2/2] 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.
---
 21.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/21.md b/21.md
index bfbb3ae..6246eb4 100644
--- a/21.md
+++ b/21.md
@@ -1,12 +1,12 @@
 NIP-21
 ======
 
-`nostr:` URL scheme
+`nostr:` URI scheme
 -------------------
 
 `draft` `optional` `author:fiatjaf`
 
-This NIP standardizes the usage of a common URL scheme for maximum interoperability and openness in the network.
+This NIP standardizes the usage of a common URI scheme for maximum interoperability and openness in the network.
 
 The scheme is `nostr:`.