That all sounds very shitty, but I think because of that it might work. I can't think of anything else better.
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s have you seen it? Is this just like Daniel's blobstr?
it is
you have the hash and a pubkey, you basically use the same technique we use with NIP-65 to find events
e.g.
* you start with a URL that includes the hash
* you get an error because the server banned the photo of nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and Dilma
* you look up who uploaded the file (either a 1063 or the author of the event where you saw the URL)
* you fetch their NIP-65-equivalent list of blossom-servers
* you HEAD or GET the file from those
that's the most direct/happy path after censorship, but you could always publish a request (ala dvms) saying "willing to pay this much for a file with this hash"
Discussion
I haven’t looked at blossom that much, from what I understand nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 just spec’d a way to do content addressable file lookups over http for redundancy, but doesn’t spec a way to distribute files to these blobstr servers.
One thing that just came to mind is a blobstr service is one that monitors these hashes and automatically mirrors them from your notes. You wouldn’t need any of the blossom machinery and would be more automated. I guess the blossom list thing would still be useful if you want to advertise which blobstr relays you use.
The only additional thing blobstr needs is authenticated uploads for uploading files. This could just be an api key and doesn’t need to involve nostr at all.
Maybe this is the same or very similar to blossom?
Seems to be pretty much the same.
What about NIP-97? This way, copies of the file can be distributed across multiple relays that choose to accept NIP-97 events, and users don't need to think about what servers to send the file to.