6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	cdf1ad85fb	telegram: say the desktop client's gap is a known one the router does not enforce (hq issue 344)	2026-10-09 12:30:56 +02:00
jschoubben	4d36997e61	telegram: take a tap only on a message showing the words this channel put there, and say where an approval from Telegram means something ... The review of 2026-10-09 (M4): another holder of the token can change a message's words and leave its buttons, so the operator taps Release under words that say something else. Each message's words are now kept as a digest, per chat and message, and a tap on a message whose words differ, or that this channel never showed, is refused on the phone and never said to the router. The README says, as the operator directed (H5), that an approval from Telegram is meaningful only where agents run under their own account without sudo, without the operator's X display, and with Telegram Desktop's data readable by the operator alone; until then, approve from the phone.	2026-10-09 12:30:56 +02:00
jschoubben	82c522ed77	telegram, desk-channel: move to mesh-sdk 7690299, whose digests are over named fields (the review of 2026-10-09)	2026-10-09 12:30:56 +02:00
jschoubben	8dbffec0fd	telegram, desk-channel: move to mesh-sdk d4077b4, where a warrant names the ask's digest (hq ADR 0259 §6)	2026-10-09 12:30:56 +02:00
jochen	906a868c46	Run telegram as its own account in a runtime of its own, keep its offset per update, and keep no copy of a secret on the desk (hq ADR 0259 §8)	2026-10-09 12:30:56 +02:00
jochen	3aa46f068a	Add telegram and the desk as channels of their own, each judging nothing and holding only its own secret (hq ADR 0259)	2026-10-09 12:30:56 +02:00