I got it, thanks.
Btw it seems that Blossom is getting more traction than nip96, isn't?
Why do you prefer nip96?
Thread
Login to reply
Replies ()
NIP96 does not prescribe how I serve the media (endpoint to be specific) and allows me to make a more reliable service with a clear separation of concerns. In blossom I am forced to accept uploads and serve media from the same exact hostname, therefore forcing me to make trade-offs that hurt speed or availability.
Serving media in Blossom can be managed with a redirect, like you do, and this offer a good degree of flexibility to separate the upload endpoint and the actual storage.
> Note that the "<sha256-hash>" part is from the original file, not from the transformed file if the uploaded file went through any server transformation.
Instead I find this part quite problematic because it does not easily permit to test the file integrity. I need a nip94 event or an imeta tag with the "x" value to check it.
Media transformation is a powerful feature but adds a lot of complexity.
Finally I don't read in the nip anything about mirroring (not only multiple uploads) of the assets, and fallbacks in the download procedure, aspects that seem important in the decentralized context of Nostr.