> no amount of UI design can really fix it.

Raw JSON

{
  "kind": 1,
  "id": "8361e997679b810f127f0af8b4e958d01281a56c1c5f5a0441a1bfd8cdcba155",
  "pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
  "created_at": 1780422069,
  "tags": [
    [
      "p",
      "c4368c512e70e36558fa167967cd73fc83a8a907ea38b3ed68358fcbdfab0da6",
      "wss://nostr.wine/",
      "Zsubmariner"
    ],
    [
      "e",
      "00c050a2c77c348847d30a636c70db53d51962dcb509861618ab230a9f8c267d",
      "wss://nos.lol/",
      "root",
      "c4368c512e70e36558fa167967cd73fc83a8a907ea38b3ed68358fcbdfab0da6"
    ]
  ],
  "content": "\u003e no amount of UI design can really fix it.\n\nThis jives with something I've been saying and feeling recently but which I hadn't identified: that widespread adoption of cryptography needs to be predicated on including a basic understanding of async crypto in secondary education curricula. It's not a hard concept, but it's like referring to the unit circle around someone who has never taken trigonometry.\n\n\u003e Software should generate dedicated keys for every relationship, connection or context.\n\nI agree with this, but it becomes tricky to map software to relationships. This is the next step in adopting cryptographic identities, but I don't know how you solve it without adding a ton of additional cognitive load for users.\n\nThe technical description itself sounds quite good, although I would be interested to see how you solve the networking layer, especially in terms of when to use direct connections, p2p technology and centralized intermediaries (like nostr relays).\n\nYou're a very good writer, I enjoyed reading this.",
  "sig": "c8bfcc8d9400824d039f55e49cf72ad2ae34d2f1beb8261934169dc77e2b321852c2c0b1847cd34ec17ea04d6fdde0cb4a8f111c0bce82f7083661a9c7841611"
}