Repository navigation
FEAT: Show replies in Telegram and Discord - #131
Merged
Merged
Conversation
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.
Replies made in Telegram or Discord now keep their context on the other messenger: Telegram gets a native reply to the original message or to the bridge's copy of it, Discord gets a small
↪ Name: textline that links to the original, and the replied text is quoted when the original is no longer remembered (restart, cache full).Telegram messages now reach the configured topic through
message_thread_idinstead of a reply to the topic's first message. New keys with defaults:tgConfig.reply_preview_length,tgConfig.relayed_message_cache_size,jdaConfig.replyPreviewLength,jdaConfig.relayedMessageCacheSize.