Global Feed Post Login
Replying to Avatar brugeman

Ok so I need a storage server integration for our product. Blossom is very simple spec focused on fighting link rot and decentralization, key to which is that uploaded files must not be modified, so my app wouldn't have to trust the server. Blossom invents it's own auth instead of nip98, needlessly.

Wrt nip96, which I didn't consider, but looking at right now, it's much more verbose and covers a lot, and uses hash for addressing, but lacks one critical thing - I want to ask the server to keep the original and do no transformations. Adding this one option would make it a superset of blossom and I would be able to use it. Maybe there's such an option and I missed it in the nip96 spec?

Avatar
hzrd149 1y ago

I initially tried to use NIP-98 auth for the blossom spec but its requirement for the "u" tag and the full domain + path of the endpoint made it only useful for uploading to a single server

For blossom I needed a single auth event that would allow users to upload a blob to multiple servers. or for the server to upload it to other servers if that was a feature the server offered

Reply to this note

Please Login to reply.

Discussion

No replies yet.