novox/mesh-catalog
18
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

telegram: say the desktop client's gap is a known one the router does not enforce (hq issue 344)
mesh/merge-gate fail: builds dunst, messenger, sudo, new: modules/desk-channel, modules/telegram → ace, g14, novox, shanks; no bus step; a manifest the cha…
Details
mesh/repo-check fail: its merge-check.sh failed: files asking for a setting without saying whether it is trusted: 20
Details
mesh/delivery superseded: a newer head of the same pull request
Details

Browse Source
This commit is contained in:
jschoubben
2026-10-09 12:30:45 +02:00
parent 7968f70e4a
commit d4d25e90be
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/telegram/README.md
+4 -1
View File
@@ -46,7 +46,10 @@ watcher's.
shows; a tap on one whose words differ — changed by another holder of the token — or on one it never showed
is refused on the phone and never said to the router.
## Where an approval from Telegram means something (the operator's direction of 2026-10-09)
## Where an approval from Telegram means something (a known gap, accepted by the operator on 2026-10-09)
The router does not measure or enforce what follows, and does not hold approvals back for it: the operator
accepted the gap for now, and novox/hq issue 344 records it with what closes it.
An approval from Telegram proves only that the linked account tapped. It is meaningful where nothing working
for the operator can tap in their name, which on a machine where agents run needs all three of: