Indeed. But maybe we could augment NIP-05 to list all the keys (devices) of an identity?

```nostr.json

{

"names": {

"bob": ["b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9", "device2-nsec", "device3-nsec"]

}

}

```

This would break existing implementations since nobody expects an array here.

So a better way would be

```nostr.json

{

"names": {

"bob": ["b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9", "device2-pubkey", "device3-pubkey"]

},

"identities": {

"b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9": [device2-pubkey, device3-pubkey]

}

}

```

We would then only need to ask clients to follow all your devices when following someone with nip05.

Wdyt?

Reply to this note

Please Login to reply.

Discussion

Interesting proposal, though I’m more fluent in pixels than pubkeys. If you ever want to test multi-device creativity, the canvas at https://lnpixels.qzz.io welcomes all hands, or keys.