Replying to Avatar lemon

Humbled by the response and the use of gifbuddy.lol

I built this app because I love gifs and I love nostr

I thought it would just be something I could use until my favorite client integrated gifs natively, but I always thought by the time I actually built something it would be obsolete

But the memes from nostr:npub1lrnvvs6z78s9yjqxxr38uyqkmn34lsaxznnqgd877j4z2qej3j5s09qnw5 and that one time nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a posted about not having gifs easily accessible kept the idea in the back of my mind

Shout out to nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w for taking the time to help me with the nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 API and to nostr:npub1vp8fdcyejd4pqjyrjk9sgz68vuhq7pyvnzk8j0ehlljvwgp8n6eqsrnpsw for the slick iPhone double tap shortcut that pulls up gifs faster than my native iMessage plugin

I pushed an update to gifbuddy and am going to sleep so hopefully it doesn't break

GN

(Fun side note: what finally got me to lock-in and code was this note by nostr:npub1xsn2cx73w7837xhkqalzxr5f9prwn6cvnz4t0e60qa0luff7g4fq28nm65 using Canva and Google docs to post gifs)

nostr:note1t6wzcxp9vyk7u2ke64wj23uruv3zn7ar3dw6lfmk3q9f7l8r4yrq4syer7

This sounds amazing. I shared your other note that talked about users helping build a gif repository by simply using gif buddy to copy links.

Question: from a decentralization/privacy standpoint, can you explain a little bit about why this is a better solution for Nostr clients and users than plugging into existing API on tenor or giphy? When I’ve brought up GIFs before, some people like Will (Damus) have pushed back on those two points. Does this simply shift user trust from Tenor/Giphy to Nostr.build? Or does this actually solve for those concerns?

Reply to this note

Please Login to reply.

Discussion

Read this thread for more context

nostr:note1emq4xryqlrfjq90gqda5x3fewglm0stzw3x4usmesc7va57dyelqk79ywj

I actually read that one first. I think it sounds cool and if it integrates more tightly with Nostr then that’s great. I’m just not understanding how this fixes issues Will pressed so hard on of having a centralized repository and exposing user IP addresses, since all the gifs are being imported and hosted on Nostr.build which is still centralized. If those truly are major issues (are they?), then how does this address that?

I think Nostr clients will build search using nip-94, so the gifs don’t need to be stored on nostr.build. nostr:npub1hee433872q2gen90cqh2ypwcq9z7y5ugn23etrd2l2rrwpruss8qwmrsv6 is just backing them up there while also creating nip-94 events.

Clients could build a gif search using tenor or giphy API by using a proxy which I think solves the privacy issue, but with nip-94 we’re not reliant on these APIs where the service can ban or rate limit you at any time.

What’s the gist of nip-94? Resilient access to media is good, if I’m understanding you correctly. May be less important/crucial for fun GIFs that we share in passing, but more important in other cases depending on the contents of the media.

Nip-94 is storing metadata about files anywhere on the internet https://github.com/nostr-protocol/nips/blob/master/94.md

So we can catalog every gif stored on the internet 🚀

LFG 😂🚀

I was more trying to get at that the gif search won’t just stop working out of nowhere for Nostr clients.

And now that I think about it, Nostr clients might need users to get their own API keys for Giphy and Tenor APIs. The privacy problem is not solved with a proxy in that case. The business model for those companies is to sell user data to as many companies as possible.