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 !

Maybe try https://github.com/nogringo/peridot

It feel so good to have a bunker that filter every app requests. I'm like a god with full power on the app.

You are sponso SimpleX or What ?

Tailscale require a KYC account

Github must be the backup not the main hosting.

I cannot access media.nostrarabia.com with https (http work fine)

Rclone is now better than ever with this new nostr remote. https://gitworkshop.dev//relay.ngit.dev/nostr-rclone-remote/tree/master/backend/nostr

I made it ! https://gitworkshop.dev//relay.ngit.dev/nostr-rclone-remote/tree/master/backend/nostr

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.

In the blossom documentation nothing explicitly mention path and it's expected because blossom just store hashs (no path and no file name). Did I miss something ? Can you point it out ?

Is there anything on the nostr ecosysteme to match a path to a hash ? I want to store files on Nostr like if it was a drive. But we need to store files path somewhere. Maybe the easyest way is just to add a "path" tag in the NIP-94 events. #asknostr #nostrdev