1. It must be mandatory and coded by all relays and all clients. Otherwise, users will see broken experiences everywhere (things appear here as official accounts of a brand but not there, etc).
2. Encryption and decryption is impossible with subkeys. For instance, we can encrypt DMs for all subkeys, but once you do it, you cannot revoke that anymore.
3. Replaceable events and all the indexing around it now must consider delegated keys whose authority can change over time on a simple re-broadcast. The entire indexing now needs to use the DB as a source for the index itself. It gets extremely complicated.
4. Now compound that complexity with the fact that we don't have a time chain on Nostr and things can appear in the past, future and different relays can and do have different versions of what's authorized at the same time.
It's mess, on top of mess, on top of mess.
All because we use raw pubkeys as the main address and not a time-resolvable DID for instance.
Vitor Pamplona
npub1gc…fnj5z
2024-09-06 13:24:38
in reply to nevent1q…gjkx
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-09-06 13:24:38Event JSON
{
"id": "50b2ce57d20539f769aa519d0ff9988e7e90921abfb0fce4cc7555b49ffef404",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1725629078,
"kind": 1,
"tags": [
[
"e",
"0e2075631621bd5015532019bacb6f46b53d2b3391ef8abac08cbbcea73b8515",
"",
"root"
],
[
"e",
"1f11f6761a55faca426d07fbae3d0caa9739c8e1fb424e0682bdabbf5b0b0644",
"",
"reply"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"587a3316c4b6374a185e37b5410142405964c2631868a8fdb77b82dcd91ca8c6"
]
],
"content": "1. It must be mandatory and coded by all relays and all clients. Otherwise, users will see broken experiences everywhere (things appear here as official accounts of a brand but not there, etc).\n\n2. Encryption and decryption is impossible with subkeys. For instance, we can encrypt DMs for all subkeys, but once you do it, you cannot revoke that anymore.\n\n3. Replaceable events and all the indexing around it now must consider delegated keys whose authority can change over time on a simple re-broadcast. The entire indexing now needs to use the DB as a source for the index itself. It gets extremely complicated.\n\n4. Now compound that complexity with the fact that we don't have a time chain on Nostr and things can appear in the past, future and different relays can and do have different versions of what's authorized at the same time. \n\nIt's mess, on top of mess, on top of mess. \n\nAll because we use raw pubkeys as the main address and not a time-resolvable DID for instance.",
"sig": "c5c4d642cef75aae90389af13bc0bb23a850fc5d4780e82aab423121ef45b3de4662675f50cb544906efc4b0c3b514708eeeb3f04c72f34484d8c28d00d8c3b3"
}