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

Merge remote-tracking branch 'origin/master' into markdownlint

Browse Source 
# By Jonathan Staab (1) and mplorentz (1)
# Via fiatjaf_
* origin/master:
  Change NIP-21 URL->URI
  Add dim tag to NIP 94

# Conflicts:
#	21.md
This commit is contained in:
Mariano Pérez Rodríguez 2023-05-01 17:22:06 -03:00
commit cd97ce5a72
No known key found for this signature in database
GPG Key ID: 695E1DF7F390D47A
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
21.md
View File

@ -1,10 +1,10 @@
# NIP-21 # NIP-21
## `nostr:` URL scheme ## `nostr:` URI scheme
`draft` `optional` `author:fiatjaf` `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:`. The scheme is `nostr:`.

4
94.md
View File

@ -2,7 +2,7 @@
## File Metadata ## 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. 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.
@ -15,6 +15,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 * `"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. * `x` containing the SHA-256 hexencoded string of the file.
* `size` (optional) size of file in bytes * `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 * `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
@ -31,6 +32,7 @@ This NIP specifies the use of the `1063` event type, having in `content` a descr
["m", <MIME type>], ["m", <MIME type>],
["x",<Hash SHA-256>], ["x",<Hash SHA-256>],
["size", <size of file in bytes>], ["size", <size of file in bytes>],
["dim", <size of file in pixels>],
["magnet",<magnet URI> ], ["magnet",<magnet URI> ],
["i",<torrent infohash>], ["i",<torrent infohash>],
["blurhash", <value>] ["blurhash", <value>]