feat: New audio downloading mechanism #113
Closed
Conversation
This file contains 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.
hi all,
i fixed the audio download issue with a new approach. due to recent changes in telegram’s interface, it's no longer possible to directly obtain the audio source link, so a different workaround was needed
this solution is to intercept requests triggered when the user plays an audio file. most of the changes are not related to the downloading itself but rather to mimicking telegram’s native interface. i have added download buttons next to the play button in audio elements and a download option in the right-click context menu
if this initial idea looks promising, i can refine it further by addressing some spinner issues and other details.
this pr should fix the issues: #101, #100, #62