draft
optional
Describes how a server could return nostr NIP-94 File Metadata tags from the /upload
and /mirror
endpoints
As described in BUD-02 servers MAY add any additional fields to a blob descriptor
Servers MAY return an additional nip94
field in the blob descriptor from the /upload
or /mirror
endpoints
The nip94
field should contain a JSON object with the keys being the tag names defined in NIP-94 and the values being strings
An example response would look like:
{
"url": "https://cdn.example.com/b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553.pdf",
"sha256": "b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553",
"size": 184292,
"type": "application/pdf",
"uploaded": 1725909682,
"nip94": {
"url": "https://cdn.example.com/b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553.pdf",
"m": "application/pdf",
"x": "b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553",
"size": "184292",
"magnet": "magnet:?xt=urn:btih:9804c5286a3fb07b2244c968b39bc3cc814313bc&dn=bitcoin.pdf",
"i": "9804c5286a3fb07b2244c968b39bc3cc814313bc"
}
}