Nostr Web Client

It's because so far, I have been able to avoid storing user uploaded images. Everything in relay tools is image links. The reasoning for that is to avoid cloud lock-in and image synchronization or processing within the cluster. (each frontend would need a copy of these user uploaded images once you go down this path).

favicons kindof breaks this, ... more likely i would just pick a better icon than the 21. like a checkmark, because self hosting is king, and anything making that more complicated is not ideal.

cloud fodder 5mo ago

and i pushed hard to get rid of favicons displays in all clients for relays for this reason, and now that i realize what jumble is doing, i'll probably try to push against that as well.. tho with relays i did not have to change nip11 i just had to get clients to use it. with this, it would probably need nip05 to have it. favicon fallback, sure thats fine. anyway, the price we pay for a tiny little image eh? 🕊️

Reply to this note

Please Login to reply.

Discussion

Silberengel 5mo ago

Our implementation was grabbing NIP-11, but many relays don't have it. Same for favicons. Best to try both.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

i baked the icon into the reverse proxy, and you can override it by adding the file next to the nostr.json :)