Used for supporting logging in to accounts with 2-factor authentication enabled.
Used to configure the underlying protocol and transport used.
Used to drive the network connection to Telegram.
Used to load and store session data, such as authorization key or current user identifier.
It also contains the logic needed to correctly process updates.
Used everywhere to invoke the "raw Telegram's API". It is the implementation of all the friendly client methods.
Telegram requires clients to send some basic system information when connecting to the server, such as OS type or system version. If these values are not explicitly provided by the user, the crate is used to load the expected values.
Similar rationale to os_info, Telegram expects a system language code used by the client
(presumably for things such as localized service messages among others).
Enables the user to use markdown text to send formatted messages.
Enables the user to use HTML text to send formatted messages.
Used to coordinate the asynchronous methods of the client.
Used to log the execution of the client to help debug issues.
Needed when uploading files to Telegram.
Used to guess the mime-type of uploaded files when sending media unless the user explicitly sets the mime-type themselves. The mime-type is required by Telegram.
Used for defining date types (for example, accessing the date of when a message was sent).
Used by the examples to showcase how one may configure logging for more information.
Used to test that this file lists all dependencies from Cargo.toml.
Used for return custom types that impl Future so that the requests can be further configured
without having to use Box.
Provides useful functions for working with futures/tasks.
Used to parse certain URLs to offer features such as joining private chats via their invite link.
Used for its web-friendly clock and timer as a replacement for std::time in the library.
Automatically falls back to std::time when we're not targeting web.