yeah, i figured that nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h had used some common type of reverse proxy that puts them on the domains by default, probably for his web app.
Discussion
and yeah, probably the web server that has the 21 icon is the one that does the nip-05s
it's tied to the nip-05 in jumble so it is simplest to just add it to the handler for the nip-05
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.
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? 🕊️