lemon on Nostr: Integrating GIF buddy into clients has been tricky because every developer is ...
Integrating GIF buddy into clients has been tricky because every developer is different
I made a GIF Buddy API for Corny Chat by
Vic :Cacodemon: :doomguy: (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
Published at
2025-02-01 16:22:13Event JSON
{
"id": "afade0c5a58fea6948a34b7925b93e37add9a9bce6223dc60591a3450a4b8e59",
"pubkey": "be7358c4fe50148cccafc02ea205d80145e253889aa3958daafa8637047c840e",
"created_at": 1738426933,
"kind": 1,
"tags": [
[
"e",
"983b259dedb519026d3116b27db1252836ad3c86552ccf116a35465ad9dc1ce7",
"",
"root"
],
[
"e",
"b61f03f04e56cc4e187ddb0e41ebd1f916b8650d9cd4b40dc6c97686d6b25fcc",
"",
"reply"
],
[
"p",
"a80fc4a78634ee26aabcac951b4cfd7b56ae18babd33c5afdcf6bed6dc80ebd1"
],
[
"p",
"c04ae0f0804c8b5ca8dfebfa1624142bebb5582f9c77a5bfdf524839b0cd5684"
],
[
"p",
"21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e"
],
[
"p",
"7fa56f5d6962ab1e3cd424e758c3002b8665f7b0d8dcee9fe9e288d7751ac194"
],
[
"p",
"266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5"
],
[
"p",
"3efdaebb1d8923ebd99c9e7ace3b4194ab45512e2be79c1b7d68d9243e0d2681"
],
[
"r",
"https://image.nostr.build/2666c8221395ab5670292d0d2d0224f5a64778d095896446403101efe09eef86.gif"
]
],
"content": "Integrating GIF buddy into clients has been tricky because every developer is different\n\nI made a GIF Buddy API for Corny Chat by nostr:npub1yx6pjypd4r7qh2gysjhvjd9l2km6hnm4amdnjyjw3467fy05rf0qfp7kza \n\nI built a tool for creating personalized GIF Collections that uses a custom NIP used in ChaChi by nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg \n\nI publish every GIF that’s copied as a public event under NIP94 that other clients can freely access like noStrudel by nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr \n\nI deployed my own relay where all the GIF related events are publically accessible under:\nwss://relay.gifbuddy.lol\n\nAnd I’m personally trying to code GIFs into nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 \n\nMy 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\n\nPart of the challenge is that Nostr clients are inherently all built so differently: web vs. native, iOS vs. Android, one programming language vs. another\n\nSlowly but surely we will get there\n\nGIFs are inevitable\n\nhttps://image.nostr.build/2666c8221395ab5670292d0d2d0224f5a64778d095896446403101efe09eef86.gif",
"sig": "e83b758584b15414d547ad6623b769255d79c19e1e933a5eda1b81c445bab10ee9d7a7886674ab89c2a5539c6316b4779d0548f513d7eef821cc581a45a546ca"
}
