plausible deniability server/relay + client:

原始 JSON

{
  "kind": 1,
  "id": "0000948cbd48da00d7a61f3675b8ce30ef4c9cf11bea965d2a4d31c84388ceb5",
  "pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
  "created_at": 1780853963,
  "tags": [
    [
      "p",
      "67ada8e344532cbf82f0e702472e24c7896e0e1c96235eacbaaa4b8616052171"
    ],
    [
      "client",
      "Wisp"
    ],
    [
      "nonce",
      "91688",
      "16"
    ]
  ],
  "content": "plausible deniability server/relay + client: \n- when you post to the server, you specify a symmetric encryption key, using that key to encrypt the content. but you don't tell the server the key\n- any client displaying the content should take a key as an argument (url param would make for easy sharing), and attempt to decrypt the cyphertext clientside using said key\n- if you provide the correct key, you can view the cleartext in the client. the server never knows what data it's storing - but for users, sharing the clear version is trivial: just share a url that includes the key.\n- extra protection: the server/relay doesn't accept any cleartext content, so there's no moderation burden.  \n\n\nnostr:nprofile1qqsx0tdgudz9xt9lstcwwqj89cjv0ztwpcwfvg674ja25juxzczjzug67kype does this get around the server owner's responsibilities re: content and liability?",
  "sig": "5c058e0f07a9832b40b25ec4e164a3937f315d6c8c9d6a4a509ab8ff330e9b3b83dbb6d87914c450dce40467053a6e6aef72594aa8483bea7e17701e7b59e3a0"
}