telegram: a refusal of a tap on changed words stays on the phone alone (issue 372 review)
mesh/merge-gate pass: builds messenger, telegram → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
mesh/merge-gate pass: builds messenger, telegram → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
The lab's proof showed it then reached a stranger's chat: whoever the buttons reached is told nothing more than the tap's own acknowledgement.
This commit is contained in:
@@ -328,7 +328,8 @@ func (c *Channel) Handle(u Update) {
|
||||
want != wordsDigest(cb.Message.Text) {
|
||||
words := "That answer was not taken: this message does not show what the mesh put there. Nothing was done."
|
||||
c.answerTap(cb.ID, words)
|
||||
c.reply(cb.Message.Chat.ID, words) // a toast goes; the chat keeps why
|
||||
// Said on the phone alone, never in the chat: the tapper may be somebody the buttons reached, who is told
|
||||
// nothing more (the lab's proof).
|
||||
c.Logf("[telegram] a tap on a message not showing what this channel put there was refused")
|
||||
return
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user