nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 23:05:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix markdownlint issues

Browse Source
This commit is contained in:
Mariano Pérez Rodríguez 2023-04-21 10:41:53 -03:00
parent 7860247937
commit 70b35bd248
No known key found for this signature in database
GPG Key ID: 695E1DF7F390D47A
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
94.md
View File

@ -1,15 +1,16 @@
NIP-94 - File Header
======
`draft` `optional` `author:frbitten`
# NIP-94 - File Header
`draft` `optional` `author:frbitten`
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.
Also the goal is to create a base on the protocol for this bountsr "Filesharing App" (https://bountsr.org/p2p-filesharing/) to be implemented.
Also the goal is to create a base on the protocol for this bountsr "Filesharing App" (<https://bountsr.org/p2p-filesharing/>) to be implemented.
## Nostr event
Nostr event
------------------
This NIP specifies the use of the `1063` event type, having in `content` a description of the file content, and a list of tags described below:
* `url` the url to download the file
* `m` 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)
* `m` 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>)
* `"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
@ -38,19 +39,18 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr
}
```
Client Behavior
---------------
## Client Behavior
The client can use this event as they see fit. Either showing events in the same feed as kind 1 events or creating a specific feed for file listings.
It allows the app to create image galleries (memes, animations) that can be reused countless times in different notes. As it exists in whatsapp, telegram, etc.
It allows the app to create image galleries (memes, animations) that can be reused countless times in different notes. As it exists in whatsapp, telegram, etc.
Example: <https://ibb.co/Fnj5TMg>
Example: <https://ibb.co/Fnj5TMg>
To do this, just select the image from the gallery (events NIP-94) and include the URL of the selected image
## Suggested Use Cases
Suggested Use Cases
-------------------
* A relay for indexing shared files. For example to promote torrents
* A Pinterest-like relay and app where people can share their portfolio and inspire others.
* A simple way to distribute configurations and software updates.