That's true, but it's harder to implement, and the only use case is interfacing with Mastodon.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
Is there an obvious reason why `@` is not allowed in the local part of a `nip05` key? It would be nice to have proxied names like `alex@gleasonator.com@mostr.pub` instead of `alex_at_gleasonator.com@mostr.pub`. Assuming it's not allowed in the domain part, there should be no ambiguity in how to look that up.