nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-21 07:15:50 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

NIP-94: Add optional 'download' flag

Browse Source 
In Stemstr, we have notes that present the same audio file as both a downloadable wav file and a streamable m3u8. We would like other clients to know that the wav is meant to be downloaded and the m3u8 is meant to be played inline.

The proposed change is adding a "download" flag to NIP-94 to signal this intent.
This commit is contained in:
Michael Hall 2023-07-08 12:31:17 -04:00 committed by GitHub
parent 141197c564
commit 2b3f5ba0eb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
94.md
View File

@ -21,6 +21,7 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr
* `magnet` (optional) URI to magnet file * `magnet` (optional) URI to magnet file
* `i` (optional) torrent infohash * `i` (optional) torrent infohash
* `blurhash`(optional) the [blurhash](https://github.com/woltapp/blurhash) to show while the file is being loaded by the client * `blurhash`(optional) the [blurhash](https://github.com/woltapp/blurhash) to show while the file is being loaded by the client
* `download` expresses that this file is intended to be presented as a download link, rather than played inline. Client's may choose to ignore this.
```json ```json
{ {
@ -37,7 +38,8 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr
["dim", <size of file in pixels>], ["dim", <size of file in pixels>],
["magnet",<magnet URI> ], ["magnet",<magnet URI> ],
["i",<torrent infohash>], ["i",<torrent infohash>],
["blurhash", <value>] ["blurhash", <value>],
["download", <boolean>]
], ],
"content": <description>, "content": <description>,
"sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field> "sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field>