GM
I've updated the profile picture and banner URL in the event kind 0 metadata for nostr:npub1phpdev2d38u5hzs4jrsh360mevh0rjctu9669quy97wu23u8sqdqpfha0j which now points to Blossom served images. Which clients does support to fallback to other Blossom servers if that domain is not available (or the file is not available anymore) to serve these pictures specific from kind 0 events just like how it's done with referenced blobs in content fields of events?
#devstr #nostrdev
/cc nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl
Thoughts?
I’ve actually implemented this logic, but I haven’t done any thorough testing yet. So I can only say that in theory it should work, haha.
This is good, but I don't have the logic implemented anywhere yet. Fallbacks might come from within the note (imeta tags), or from blossom servers for the note author, or other heuristics. Selecting these isn't super well defined right now as far as I know.
Gossip isn't doing it. I think the idea was that any url ending in enough hex digits might be blossom and to do that. But I never got around to it, and I've become busy with things outside of nostr, at least for a while.
