I know NIP-05 is "centralized" and we need a better solution, but what are your thoughts on adding (optional) alias support to NIP-05 for users with several registered NIP-05 pointers? Seems like it could be useful with platforms that want to integrate or fully offload ID to npubs via NIP-05 registrations and allows users to list aliases from any service providers that support NIP-05 vs the NIP-39 lists that seem to be scoping platform IDs that do not support native nostr driven auth. I am hoping that others see the idea as a viable and worthwhile addition to make nostr login and registrations easier for platforms that want to participate, centralized or decentralized. Even if we add other, more sovereign features, the ecosystem grows with more integrations and development of service providers or protocol enhancements that come from wider adoption and use.

GitHub

Extend NIP-05 for optional multi-identifier support in profiles by imp0stor · Pull Request #1991 · nostr-protocol/nips

This NIP proposes an extension to user profile metadata (kind 0 events) to support multiple NIP-05 identifiers as aliases. This allows users to ass...