CXPLAY on Nostr: Why are all the NIP-94 implementations server-side only, especially the NIP-96 ...
Why are all the NIP-94 implementations server-side only, especially the NIP-96 server, and is it really only the server that can compute the metadata for a file? Why isn't this process done on the client side, and if I insert a random network memes does that mean I'll never be able to add the metadata that makes sense to the client (unless I consider writing event JSON manually)?
As far as I know, all the file metadata for the NIP-35 for Torrent indexing is client-supplied, and users can even fill it in themselves, but somehow it's become a server-only affair with the NIP-96.
#nostr #asknostr
Published at
2025-04-11 19:32:16Event JSON
{
"id": "a3c3fa4e6c5e97fbda653dc9f84c496f41ec5d513bb8e5fc66a60c227c0e3946",
"pubkey": "434f97993627f1e61f14eeaf60caa8cfdcec10a592caff8250c825252d548c15",
"created_at": 1744399936,
"kind": 1,
"tags": [
[
"t",
"nostr"
],
[
"t",
"asknostr"
],
[
"client",
"Nostr.moe",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1743748820"
]
],
"content": "Why are all the NIP-94 implementations server-side only, especially the NIP-96 server, and is it really only the server that can compute the metadata for a file? Why isn't this process done on the client side, and if I insert a random network memes does that mean I'll never be able to add the metadata that makes sense to the client (unless I consider writing event JSON manually)?\nAs far as I know, all the file metadata for the NIP-35 for Torrent indexing is client-supplied, and users can even fill it in themselves, but somehow it's become a server-only affair with the NIP-96.\n\n#nostr #asknostr",
"sig": "911a211d3e441156085be93fb86e3cf4c40a70c969b6c1cc8849cd320bf7239c7a6c60d2e452a884b43577e7b25cebcaa181deeedce4e0d20edf86ba1fa7ad91"
}