Thanks for building it! Is it FOSS?
Enabling DNSSEC for nip05.site if possible, makes sense.
> or CORS headers
That then appears to be a workaround for those who don't follow NIP-05 properly. The TLS cert requirement for clearnet could also be added to the spec (as well as I expect it won't be properly followed too).
I worry about TLS in particular; it's a weak way to verify authenticity but still a way. With a proxy, it's not clear whether the response was authentic.
What would make a lot of sense, though, is proxying onion/i2p/fips/dnn/etc., because their authenticity is verifiable. This would make NIP-05 work in clearnet for domains that can't be taken down in exchange for trusting nip05.site. But that, of course, opens a question of why not have a more general proxy that could proxy non-clearnet relays as well.
nevent1qqsv2nn432q…
Enabling DNSSEC for nip05.site if possible, makes sense.
> or CORS headers
That then appears to be a workaround for those who don't follow NIP-05 properly. The TLS cert requirement for clearnet could also be added to the spec (as well as I expect it won't be properly followed too).
I worry about TLS in particular; it's a weak way to verify authenticity but still a way. With a proxy, it's not clear whether the response was authentic.
What would make a lot of sense, though, is proxying onion/i2p/fips/dnn/etc., because their authenticity is verifiable. This would make NIP-05 work in clearnet for domains that can't be taken down in exchange for trusting nip05.site. But that, of course, opens a question of why not have a more general proxy that could proxy non-clearnet relays as well.
nevent1qqsv2nn432q…