I was thinking how we could add nostr into rclone
https://github.com/rclone/rclone
I use this tool quite a lot on different machines
So I was listening to nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcprpmhxue69uhhyetvv9ujuer9wfnkjemf9e3k7mf0qyd8wumn8ghj7ur4wfshv6tyvyhxummnw3ezumrpdejz7qpqdergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsce9rzs and nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qyghwumn8ghj7mn0wd68ytnvv9hxgtcqyqnxs90qeyssm73jf3kt5dtnk997ujw6ggy6j3t0jjzw2yrv6sy22vuwtly talk about replicating content across relays this morning, and so I wrote replicatr:
https://github.com/coracle-social/replicatr
Replicatr is a daemon which listens to one or more indexer relays for `kind 10002` events. When it detects a change in any user's relay selections, it uses negentropy to sync that user's notes to their new relays based on the outbox model.
The neat thing is you don't have to run one. I deployed one this morning which points to indexer.coracle.social, so if your metadata gets published there (or to any of the relays that it mirrors), you're already covered (unless your new outbox relay rejects replicatr's publishes).
Discussion
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 !
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.
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.
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.