upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorfrbittencourt <fbittencourt@neadvance.com>2023-03-10 10:18:53 +0000
committerfiatjaf_ <fiatjaf@gmail.com>2023-04-20 08:06:14 -0300
commit747517f2c462ad603ee5b0b75c20693ef3913363 (patch)
tree4204839112d54344f9f7b10cbcdf1d726f4337bf
parent9d69bd05dcdaa1ee19078937a6150e2720bf9ba5 (diff)
ajusts description of decrypt tag
-rw-r--r--94.md2
-rw-r--r--95.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/94.md b/94.md
index 51ec1e2..7051ee6 100644
--- a/94.md
+++ b/94.md
@@ -11,7 +11,7 @@ This NIP specifies the use of the `30063` event type (parameterized replaceable
11* `d` containing the name of the shared file to allow it to be overwritten in the future. 11* `d` containing the name of the shared file to allow it to be overwritten in the future.
12* `url` the url to download the file 12* `url` the url to download the file
13* `type` a string indicating the data type of the file. The MIME types format must be used (https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types) 13* `type` a string indicating the data type of the file. The MIME types format must be used (https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
14* `decrypt` (optional) If the file is encrypted, you must indicate in the first value the algorithm used to encrypt the file and in the second value the information (the key) that allow the decryption of the file 14* `decrypt` (optional) If the file is encrypted, you must indicate in the first value the algorithm used to encrypt the file and in the second value the parameters that allow the decryption of the file
15 15
16```json 16```json
17{ 17{
diff --git a/95.md b/95.md
index 292d04c..00132df 100644
--- a/95.md
+++ b/95.md
@@ -9,7 +9,7 @@ Nostr event
9This NIP specifies the use of the `30064` event type (parameterized replaceable event), having in `content` the binary data that you want to be stored in Base64 format. 9This NIP specifies the use of the `30064` event type (parameterized replaceable event), having in `content` the binary data that you want to be stored in Base64 format.
10* `d` containing the name of the shared file to allow it to be overwritten in the future. 10* `d` containing the name of the shared file to allow it to be overwritten in the future.
11* `type` a string indicating the data type of the file. The MIME types format must be used (https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types) 11* `type` a string indicating the data type of the file. The MIME types format must be used (https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
12* `decrypt` (optional) If the file is encrypted, you must indicate in the first value the algorithm used to encrypt the file and in the second value the information (the key) that allow the decryption of the file 12* `decrypt` (optional) If the file is encrypted, you must indicate in the first value the algorithm used to encrypt the file and in the second value the parameters that allow the decryption of the file
13 13
14This event must not be returned in generic searches. It should only be returned if specifically requested by your ID. This avoids bandwidth consumption and unnecessary overload on the relay and client. 14This event must not be returned in generic searches. It should only be returned if specifically requested by your ID. This avoids bandwidth consumption and unnecessary overload on the relay and client.
15 15