frphank on Nostr: The chain of messages can be forked in double ratchet. However, any message has a ...
The chain of messages can be forked in double ratchet.
However, any message has a "previous message" like any commit in git has an ancestor. This provides important context, as to understand a message you need to know what previously transpired in a chat.
If your attacker doesn't know whether he has all the messages neither does the legitimate recipient and will as such have trouble comprehending the conversation. Your "it's not a bug it's a feature" doesn't work here.
Published at
2025-03-21 17:39:55Event JSON
{
"id": "9eaf7b5a5ce08b1a2ef4f1d8c46de1f46b746934781ea578cc677994e47d989b",
"pubkey": "47be0b2a89faaa66bc57f5c679203486da45660295cb3db3c2f38f4be8d8816e",
"created_at": 1742578795,
"kind": 1,
"tags": [
[
"e",
"a528f919cbf13d8d584a98a6ff785dcc6f5fb847660f8d62549249977bd922e2",
"",
"root"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
]
],
"content": "The chain of messages can be forked in double ratchet.\n\nHowever, any message has a \"previous message\" like any commit in git has an ancestor. This provides important context, as to understand a message you need to know what previously transpired in a chat.\n\nIf your attacker doesn't know whether he has all the messages neither does the legitimate recipient and will as such have trouble comprehending the conversation. Your \"it's not a bug it's a feature\" doesn't work here.",
"sig": "23ff675765ee2511b259759dddff105054ffd3ee487cc6fefc43409c49664fca0c8c7d6bec3b97429fc07dd05473e7f9048c1af3d19599bfa169fdc8919b8f74"
}