nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 had an interesting suggestion: File Hosts could create a NIP-94 event (signed by them) when returning the uploaded image URL to a Nostr client.
Then they could easily track the use of their images in the Nostr ecosystem: Receive reports, notifications of use (quote), replies and likes to the image directly, and even direct zaps for hosting the image.
Great middle ground 👏
This seems nice.🚀
Another use case for split zaps maybe, too? Like when a file hoster hosts a nip94, they could take x% of received zaps for doing so. Users can choose hosts based on fee rate, reliability etc? It's free to use them but if people like the content, hosts could benefit by a small percentage of the zaps to make hosting more sustainable?
Can you explain further how this would work?
Someone uploads a file on my server. I publish a NIP-94 event. What do I give back to them to paste into their Nostr post? The URL or the nevent ID?
If I also give them the URL, what happens when they use that in a client that supports NIP-94? Is yet another NIP-94 event created? How exactly is that event linked to mine? Is it just a matter that that they both will be returned by any client that's looking for a file with that hash?
Could I publish the NIP-94 event after the fact?
Also - am I correct in thinking NIP-94 can't really be used to facilitate the equivalent of srcset? It's too bad images weren't thought about more when it was being developed. It would be great if you could find all the sizes of a particular image - but each size has a different hash and NIP-94 is one hash per event, right?
