Skip to content

feat: recall a Zalo message by reacting with 🙈 in Telegram - #46

Merged
williamcachamwri merged 1 commit into
williamcachamwri:mainfrom
ntdatt812:feat/recall-by-reaction
Jun 21, 2026
Merged

williamcachamwri merged 1 commit into
williamcachamwri:mainfrom
ntdatt812:feat/recall-by-reaction

Conversation

@ntdatt812

Copy link
Copy Markdown
Contributor

Telegram never notifies bots when a message is deleted, so a plain delete in the topic can't be mirrored to Zalo. Reacting with a dedicated emoji is the closest one-tap gesture the Bot API delivers.

Reacting 🙈 on a message now recalls it on Zalo (reusing the /recall undo logic for both TG→Zalo sends and Zalo→TG forwards) and deletes the Telegram copy so it disappears on both sides. The trigger emoji is intercepted before the reaction-forwarding path and is never sent to Zalo as a reaction.

Duplicate reaction updates are deduped to avoid a double undo, the Telegram copy is removed only after a successful recall, and failures report back into the topic.

Telegram never notifies bots when a message is deleted, so a plain
delete in the topic can't be mirrored to Zalo. Reacting with a
dedicated emoji is the closest one-tap gesture the Bot API delivers.

Reacting 🙈 on a message now recalls it on Zalo (reusing the /recall
undo logic for both TG→Zalo sends and Zalo→TG forwards) and deletes
the Telegram copy so it disappears on both sides. The trigger emoji is
intercepted before the reaction-forwarding path and is never sent to
Zalo as a reaction.

Duplicate reaction updates are deduped to avoid a double undo, the
Telegram copy is removed only after a successful recall, and failures
report back into the topic.
@williamcachamwri
williamcachamwri merged commit eee0676 into williamcachamwri:main Jun 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants