@mint @rees @NEETzsche @malakai You define your @ in your profile, then clients verify it from the well-known endpoint. Multiple nostr.json's are just multiple options for names you can become.

The main problem with bridging this is exactly the flexibility it provides. Fedi software can't handle it. It needs to be a stable name, therefore it uses the pubkey.