We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Media size limitation passed with URL is different in each case.
InlineQueryResultPhoto - 5 MiB InlineQueryResultMpeg4Gif - 1 MiB InlineQueryResultGif - 1 MiB InlineQueryResultDocument - provides no size limitation
InlineQueryResultPhoto
5 MiB
InlineQueryResultMpeg4Gif
1 MiB
InlineQueryResultGif
InlineQueryResultDocument
While in reality all support files up to 10 MiB and up to 20 MiB in local mode. Is this a mistake or the documentation is outdated?
10 MiB
20 MiB
The text was updated successfully, but these errors were encountered:
While in reality all support files up to 10 MiB and up to 20 MiB in local mode.
This makes no sense. There is no a single difference in handling of files uploaded by URL in local mode compared to api.telegram.org.
Sorry, something went wrong.
While in reality all support files up to 10 MiB and up to 20 MiB in local mode. This makes no sense. There is no a single difference in handling of files uploaded by URL in local mode compared to api.telegram.org.
Yes, specifically this makes no sense. It's always up to 20 MiB despite the documentation.
No branches or pull requests
Media size limitation passed with URL is different in each case.
InlineQueryResultPhoto
-5 MiB
InlineQueryResultMpeg4Gif
-1 MiB
InlineQueryResultGif
-1 MiB
InlineQueryResultDocument
- provides no size limitationWhile in reality all support files up to
10 MiB
and up to20 MiB
in local mode.Is this a mistake or the documentation is outdated?
The text was updated successfully, but these errors were encountered: