Search is clearly Discovery
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 I’m as disappointed as nostr:npub1lrnvvs6z78s9yjqxxr38uyqkmn34lsaxznnqgd877j4z2qej3j5s09qnw5 about not having gifs in any nostr client
Seems like I could make a DVM for this to shield client developers from data extraction being associated with their app
But I think this would constitute a new event kind and I don’t know a gif search is considered 52XX Image Manipulation or 54XX Discovery, thoughts?
nostr:note19wredrv34rc9w6c3e4c47e96pyuwgnw5k8c2zha9lqumppv3t43qrz70h0
Discussion
I’m inclined to agree, but it is funny that the two first people to reply said different things
I was more probing to see if anyone has had thoughts on a Gif DVM before and if there’s any down sides I might be missing
Mostly concerned about speed right now
if i were to implement i would not use DVMs. instead, spec an interface, allow for pubkey and payment provided in headers, and return json results that include publicly accessible URIs
So you’re thinking basically a simple HTTP GET request API for clients to use, yeah?
And then on the back end I can use Giphy or Tenor or whatever gif API service provider, but then open source it to show that search results aren’t stored/sold/paired with user data?
I just don’t want to have to build out my own gif repository; I wasn’t even planning on charge for the service
I just want gifs
yeah. you could basically act as a proxy to giphy, tenor, google image search, midjourney or whatever.
I see what you’re saying, I just don’t know if that’s “enough” for client developers to adopt it, but I can try it out and see how it goes
Thanks for the back and forth, if you have any other recommendations let me know
I’ll open source it so it’s transparent on what’s going on, but should be really simple 👍