NIP-11 has an optional icon field https://github.com/nostr-protocol/nips/blob/master/11.md#icon please set it so relay explorers and other clients can show it 🙏
Discussion
Many relays just set /favicon.ico
That's fine, just that favicon.ico is usually low resolution, not beautiful to display as large image
In nostrrr.com I use NIP-11 icon if available and favicon if not. Still most relays don't have either 😿
Wow, it's awesone! Does nostrr.com have a public API? I need to implement a "relay recommendation" page but writing a relay discovery algorithm is a big task.
It's using NIP-66 https://github.com/nostr-protocol/nips/pull/230 events for relay discovery via wss://history.nostr.watch I was using nostr.watch API before but I'm now getting the data from the nostr. I'd tag sandwich but don't know his npub 😸
yeah, i had a funny encounter with fiatjaf over this because it took me less than a day to add NIP-11 support to my fork of khatru and he said "khatru doesn't support NIP-11 so it can't report what NIPs it supports"
laziness
Is worth sending a patch to khatru to add support for NIP-11 imo, as a relay explorer dev it's annoying when relays don't have it.
lol, i had to rewrite so much of the codebase it's futile to try and patch
i gave everything logical names and reduced the amount of work it does decoding JSON, chased down a dozen concurrency bugs and NIP-11 for one thing, and a whole heap of other things
really, it was intentional to provide a framework to build something better, but anyone who tried to use go-nostr who isn't experienced with working with go would be oblivious to how badly it's architected and implemented
yes the roof is above the foundations but that's about as far as the correctness goes