Repository navigation
feat: mirror Zalo typing and seen indicators into Telegram - #45
Merged
williamcachamwri merged 1 commit intoJun 21, 2026
Merged
williamcachamwri merged 1 commit into
williamcachamwri merged 1 commit into
Conversation
Surface two presence signals from Zalo in the linked Telegram topic: - typing: when a Zalo peer is composing, refresh the topic's "typing…" chat action (throttled per thread, auto-clears after ~5s). - seen: when a peer reads a message sent from Telegram, add a 👀 reaction to the originating Telegram message (deduped per message). Both are strictly Zalo→Telegram and read-only on the Zalo side: no extra outbound Zalo traffic is generated, so account-ban risk is unchanged. Memory for throttle and dedupe state is bounded.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surface two presence signals from Zalo in the linked Telegram topic:
Both are strictly Zalo→Telegram and read-only on the Zalo side: no extra outbound Zalo traffic is generated, so account-ban risk is unchanged. Memory for throttle and dedupe state is bounded.