lemon on Nostr: I'm considering building a Javascript SDK for GIF Buddy I'm just brainstorming the ...

I'm considering building a Javascript SDK for GIF Buddy

I'm just brainstorming the idea now and am not entirely sure if it's the best approach, but I think the Software Development Kit would need to include:
- NIP94 media search (memes, GIFs, mp4 uploads)
- Semantic search ordered by relevance
- Search by relay
- GIF & meme collections by npub
- Event publishing to edit collections and build media repositories
- No API limits or API keys/Nostr-native

This could be helpful for Nostr Clients that use React Native (like Olas) or Web Clients (like noStrudel)

It wouldn't be as beneficial to native iOS clients (like Damus) and it would likely take some time to figure out

Would this be worthwhile?
hzrd149 (nprofile…tyk0) PABLOF7z (nprofile…478g) verbiricha (nprofile…xfv5)
#asknostr

quoting nevent1q…zy98

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

I made a GIF Buddy API for Corny Chat by Vic (npub1yx6…7kza)

I built a tool for creating personalized GIF Collections that uses a custom NIP used in ChaChi by verbiricha (npub107j…ncxg)

I publish every GIF that’s copied as a public event under NIP94 that other clients can freely access like noStrudel by hzrd149 (npub1ye5…knpr)

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 damus (npub18m7…q955)

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