I hope he's working on that.

Reply to this note

Please Login to reply.

Discussion

Integrating GIF buddy into clients has been tricky because every developer is different

I made a GIF Buddy API for Corny Chat by nostr:npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kza

I built a tool for creating personalized GIF Collections that uses a custom NIP used in ChaChi by nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg

I publish every GIF that’s copied as a public event under NIP94 that other clients can freely access like noStrudel by nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

I deployed my own relay where all the GIF related events are publically accessible under:

wss://relay.gifbuddy.lol

And I’m personally trying to code GIFs into nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955

My goal is to have GIFs (and even memes) in every client, but trying to build a single thing that satisfies each developer has been a challenge so much of my work has been split and pulled into different directions

Part of the challenge is that Nostr clients are inherently all built so differently: web vs. native, iOS vs. Android, one programming language vs. another

Slowly but surely we will get there

GIFs are inevitable

Nothing stops this meme train

One thing they have in common.

Nostr.

Don’t build APIs.

What about SDKs?

nostr:note19t28p56sv6khf9kdxchmkfrvune3lf6d5adfy5yr8rk9urflekksm5s052