Open
Conversation
Add a new function for fetching history ranges between a max and a min id. This can come handy for fetching history deltas in supergroups on login when only the min_id is known.
Fix reported by @spaeps in majn/telegram-purple#238 Closes #42 I didn't actually do anything, except forward this patch.
The referenced target "gen-mime-types" was wrong anyway.
./auto-static-autocomplete.c:72:1: error: control reaches end of non-void function [-Werror=return-type]
|
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer; |
32-bit runtime assert fix
make tgl work with openssl
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
5 participants
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.
Allow fetching message history between max_id and min_id in a new api call. This is needed for fetching channel history when the amount of required amount of messages is unknown.
Additionally allow fetching more than 100 channel messages. I don't know why it was disabled in the first place, but I tested it thoroughly and the history function doesn't have any issue handling the channel return type CODE_messages_channel_messages.
A last change is to use less confusing naming in get_history_extra struct, offset_id is now actually called offset_id except of max_id.