To me it looks like I described in point 3:
Let's say users can mark account migrations in their follow list. They select a user they are following and click a button to add information about a migration. This could be in response to the affected user contacting them out-of-band or because they encountered some migration event like Pablo's kind:1777. In their contact list it will store the old and new pubkeys for a user with some optional explanation.
This means my client can pick this up and show me a little info box or an icon on any note from the old or new key, that will tell me something like "3 of your network are following a new pubkey for this contact". I can then click it to get a detailed view of what the old and new accounts posted, information about who of my network already confirmed it, and why, and I can then decide if I want to signal that I migrated on my contact list as well or if I want to follow both keys for now, or if I want to ignore it.
It's just more information for the user to make a decision, this particular feature would not make any automatic changes.
bu5hm4nn /
npub1hl…dz5wg
2023-11-03 02:55:56
in reply to nevent1q…hwph
Author Public Key
npub1hlq93jdtkfg29a8s7fqzzzh82q3pkc20rxucwt4geh6e56wk3y2qxdz5wgPublished at
2023-11-03 02:55:56Event JSON
{
"id": "0000022e0c25f151feb58f52f1d26c97b99be8e51db16fca5566e797643c5865",
"pubkey": "bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914",
"created_at": 1698980156,
"kind": 1,
"tags": [
[
"client",
"gossip"
],
[
"p",
"1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805"
],
[
"e",
"00000341e87b6a7197701ee6efc713200f45e3a0c737fac5f2dd85c1e75f078a",
"wss://relay.damus.io/",
"root"
],
[
"e",
"6a049a75fdf55394323bce499ca997e6bff6ea1730aa64322ebc0635531cfc4d",
"wss://relay.damus.io/",
"reply"
],
[
"nonce",
"14757395258969040872",
"22"
]
],
"content": "To me it looks like I described in point 3:\n\nLet's say users can mark account migrations in their follow list. They select a user they are following and click a button to add information about a migration. This could be in response to the affected user contacting them out-of-band or because they encountered some migration event like Pablo's kind:1777. In their contact list it will store the old and new pubkeys for a user with some optional explanation.\n\nThis means my client can pick this up and show me a little info box or an icon on any note from the old or new key, that will tell me something like \"3 of your network are following a new pubkey for this contact\". I can then click it to get a detailed view of what the old and new accounts posted, information about who of my network already confirmed it, and why, and I can then decide if I want to signal that I migrated on my contact list as well or if I want to follow both keys for now, or if I want to ignore it.\n\nIt's just more information for the user to make a decision, this particular feature would not make any automatic changes.",
"sig": "454e82da0e772289d0ecc2e07e524de05e83a773a2aa64d43c3503a0b755571468c052ebf5b0afdbc4dd0bd2cfcbb8c23813861e50ebfa85e5733ecb70cfdb06"
}