nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 one for https://nostrapps.com
Discussion
You have been chosen to send a patch for it.
Let me know when you have done it.
I couldn’t find it on GitHub and couldn’t see a way to submit a new app on the site.
Sorry nostr:npub1hee433872q2gen90cqh2ypwcq9z7y5ugn23etrd2l2rrwpruss8qwmrsv6 I meant there’s no way to submit an app on https://nostrapps.com
Building static paths to serve files (gifs on this case) is not a good path for decentralization. It would be better to store the sha256 of the file on the note and then query the relays if they have that hash on their disks.
This way you don't care which server the file is coming from, it might even be cached on the machine and notes will be future-proof like the rest of nostr.
That’s what nip94 allows for and that’s what gets published once it’s uploaded to nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7
If you read the specification, a nip94 event has the sha256 hash, a url and a fallback url
The url is convenient right now because no clients that I’m aware of query sha256 hashes like you are mentioning; however, this process sets up that foundation to be possible in the future for clients to query hashes like you’re proposing
Thank you for the note, hadn't read that NIP yet. Happy these issues got addressed beforehand. Plus points for the torrent field inside.
I will pack everything inside a zip archive and then use NIP94 for sharing it.