From b3454246f4caf0b50d535ef84bf6e052405394bb Mon Sep 17 00:00:00 2001 From: arthurfranca Date: Wed, 7 Aug 2024 12:12:49 -0300 Subject: [PATCH] Update 96.md --- 96.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/96.md b/96.md index be709991..301031f4 100644 --- a/96.md +++ b/96.md @@ -84,7 +84,9 @@ See https://github.com/aljazceru/awesome-nostr#nip-96-file-storage-servers. ## Auth -When indicated, `clients` must add an [NIP-98](98.md) `Authorization` header (**optionally** with the encoded `payload` tag set to the base64-encoded 256-bit SHA-256 hash of the file - not the hash of the whole request body). +When indicated, `clients` must add an [NIP-98](98.md) `Authorization` header. +The NIP-98 event can **optionally** include the encoded `payload` tag set to the hex-encoded 256-bit SHA-256 hash of the file - not the hash of the whole request body. +The event may include multiple `u` tags to make it possible to reuse the same header for different servers. ## Upload @@ -94,7 +96,7 @@ When indicated, `clients` must add an [NIP-98](98.md) `Authorization` header (** List of form fields: -- `file`: **REQUIRED** the file to upload +- `file`: **REQUIRED** the file to upload. It should be the last form field; - `caption`: **RECOMMENDED** loose description; - `expiration`: UNIX timestamp in seconds. Empty string if file should be stored forever. The server isn't required to honor this. - `size`: File byte size. This is just a value the server can use to reject early if the file size exceeds the server limits.