I took your advice and built a gif nostr companion app:

https://gifbuddy.lol/

You can download the PWA to your home screen, search for your gif, copy the address and paste it into your client

On the back end, for every gif that gets copied/clicked, an API request is made to upload to nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 by nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w

From there a nip94 request is done so that the content can be accessed by any client in the future

Now, anyone who searches for gifs using this tool is also helping to build the gif repository for nip94 and adding fallback urls to nostr.build

And all they did was click to copy #gifs

Reply to this note

Please Login to reply.

Discussion

I never thought that seeing Bandido doing some headscissors on nostr.

👀

nostr:npub1vp8fdcyejd4pqjyrjk9sgz68vuhq7pyvnzk8j0ehlljvwgp8n6eqsrnpsw zapped ⚡️10,000 sats

nostr:note1emq4xryqlrfjq90gqda5x3fewglm0stzw3x4usmesc7va57dyelqk79ywj

🫡🫡🫡

nostr:nprofile1qqstuu6ccnl9q9yvejhuqt4zqhvqz30z2wyf4gu43k404p3hq37ggrspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq32amnwvaz7tm9v3jkutnwdaehgu3wd3skueq4kymtq you've got me scrolling rapidly specifically looking for notes I want to respond to via gif

nostr:note1emq4xryqlrfjq90gqda5x3fewglm0stzw3x4usmesc7va57dyelqk79ywj

Great!

Too many gifs in my feed! 😂😂😂

Testing

Hmm now i have a link to tenor?

It gives tenor link and does upload async after that.

So it comes into effect if tenor decides to take down the media or dies, as a backup source. Nice.

Nice code

Smooth!

I test

Neat!

could it finally be true

so good I accidentally did it twice

Nice and useful work!

I would suggest reflecting the research as permalinks, to make it easily shareable.

The copy gif url on touch feature is nice!

And it also uploads it to nostr.build in the background.

let's test this going waaaay back...

nostr:note1emq4xryqlrfjq90gqda5x3fewglm0stzw3x4usmesc7va57dyelqk79ywj

Nice work!

It's hustle like this that I think is so interesting when it comes to the power of open protocol's

It's in everyone's interest to improve things... VERY powerful network effect long term

Now I need to work out how to do what you're saying!

It works!

This is incredible and you accidentally made my new favourite gif search in the process. Ty

Me entering the arena after nostr:npub1hee433872q2gen90cqh2ypwcq9z7y5ugn23etrd2l2rrwpruss8qwmrsv6 gave this new gif super power.

Lfg!

🔥 so nice

Droideka cat 😳

LFG

Testing

Amazing work - well done and thank you 🫂

Wow! It's so fast too! Any way to keep scrolling down to see more gifs?

If I can’t find a specific gif, is there a way for me to add it?

Looks like it's grabbing from tenor. You can create an account there and upload

That makes a lot of sense. I think I have some from giphy too. Thanks man!

nostr:note1emq4xryqlrfjq90gqda5x3fewglm0stzw3x4usmesc7va57dyelqk79ywj

This app is cooking!

I did have to save it to my phone first I didn't see an option like that but it worked heck yeah

Awesome! It works!

nostr:note1emq4xryqlrfjq90gqda5x3fewglm0stzw3x4usmesc7va57dyelqk79ywj

Very proud!!!!

Nice!

it's not copying the new URL. Only taking the tenor one. It says it is copied but isn't maybe you need a prompt for brave to ask permissions to use the clipboard? Brave on Linux Mint. If it showed the full url in the pop up it could also manually be copied.

The copied link is a Tenor link by intent

When you click a gif, a separate API call is made on the back end to upload to nostr.build

That process takes time that would really hinder the user experience if you had to wait for the new url to be generated in order copy it; it’s several seconds

I could potentially make a separate API that will return URL instantly, and will redirect to Tenor while upload is prepared, and then serve local copy. If you are interested, let me know.

There have been a couple comments in my feed from people expecting to paste a nostr.build address so that could be cool

Your API is fast already, it's mostly that nip98 AUTH requires me to publish a Kind 27235 note, which takes time to broadcast with my current library

Were you thinking this API would be separate from nip98?

Nip98 does not require anything, just a signed header. You are talking about nip94, that can be pushed async.

I would probably need that for user uploaded gifs actually now that I think about it more

Well done

Hello is this the comment section that sucks your data plans balls dry?

Awesome, thanks!

nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac one for https://nostrapps.com

Fiatjaf runs it now

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 one for https://nostrapps.com

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.