Every value an approval sets is in the note, whole where the sender is proven; the note is kept whole (issue 383)

The review of mesh-controller #304: a proposal of more than three keys showed only the names of the rest, and its Details could carry no value, so Approve bound values the operator never saw. The router now shows an ask's WholeDetails in the note in place of its Details on a kind that proves who answers, held to the secret rule alone, and refuses an ask whose whole details carry a secret's shape. Telegram keeps the note whole when a message is too long, cutting the body first and saying so, and escapes the note as every other part. SDK at mesh-sdk f474544.
2026-10-13 17:02:21 +02:00
parent 77f8481881
commit 5dbf53e758
17 changed files with 137 additions and 40 deletions
@@ -136,7 +136,9 @@ condition's message. A warning kept quiet is also said once after a day.
 explanation alone — a summary, then at most three points (`asks.Glance`; an ask that does not hold to it is shown
 and said in the log). Everything else is the message's note (`asks.Message.Note`), which a channel shows apart and
 smaller: who asked and when, with what happens if nobody answers; what each answer does; where else it is answered;
-and the asker's Details (who proposed it, a fingerprint, how to read it whole). Answered, the message is one line —
+and the asker's Details (who proposed it, a fingerprint, how to read it whole) — on a kind that proves who answers
+and was given the ask's answers, its Details whole (`asks.Ask.WholeDetails`): every value an approval sets, held to
+the secret rule alone, as the whole words are. Answered, the message is one line —
 "You chose Approve at 16:06 on Telegram · <headline>" — and the router's word on the asker is its note.

 **An ask's values are shown whole where the sender is proven** (hq issue 383). An ask may carry its explanation