It seems that serving NIP-05 nostr.json with a correct "Access-Control-Allow-Origin" header is not common at all. To the degree that it's not useful at all in web clients to show all the warnings. It's a distraction ritght now.
Maybe we could solve that with DVMs fetching and caching nip-05 data.
Login to reply
Replies (2)
I’d love to see this be part of bip353 more often also signed with DNSSEC ✌️seems to be something also forgotten allot of the time
Yes, its only worth showing if it validates.