Replying to Avatar Russell

I also think about it. The probleme is Blossom servers do not store file path nor file name but only hash. So we need somewhere a db that store the path to hash matchs.

I see 2 solutions:

Solution 1 is to create a centralized middle server that expose a S3 api to the end user (rclone will talk to this server) and this server will process the user request using nostr and blossom.

Solution 2 is to create a dedicated rclone remote for nostr + a new NIP to match the file path with the file hash.

I prefer the solution 2 but it's more complex to achieve. I will be happy to work on that project, I want it too !
Avatar
hodlbod 2mo ago 💬 2

There is this: https://github.com/nostr-protocol/nips/blob/master/94.md which can be used to map hashes to names. rclone looks great, and nostr would be a natural fit.

Reply to this note

Please Login to reply.

Discussion

Avatar
Russell 2mo ago

Yes, it's the more suitable NIP for this purpose but it do not explicitly explain how to add the path + filename. I was thinking about adding a "path" tag to make it clear where the file is in the tree.

Do you have an idea for the path ? Because we need the path somewhere.

Avatar
hodlbod 2mo ago

I don't think it would be bad to just add a `path` tag to that event, but I'm not really sure how people are currently using it, or how bad not having a path would be.