Reintroduce max_telegram_delete#1083
Open
MrAnno wants to merge 1 commit into
Open
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
1 participant
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.
This PR reintroduces
max_telegram_delete, which disappeared during the Go rewrite.The option can be used to specify the maximum number of simultaneous Telegram message deletions to handle.
In the Python bridge, it was a load/performance-related option, but I found it extremely useful for avoiding accidental or reckless deletion. Telegram has a "delete all messages on both sides" button, which can remove years of memories with two button presses...
The default was
10in Python; here I set-1in order not to change the original Go behavior.Checklist