How far the last quota check needs to be in the past to be checked by the background function (in seconds).
only an indicator in a chatlist
only an indicator in a chatlist
larger chat IDs are βrealβ chats, their messages are βrealβ messages.
messages that should be deleted get this chat_id; the messages are deleted from the working thread later then. This is also needed as rfc724_mid should be preset as long as the message is not deleted on the server (otherwise it is downloaded again)
Message length limit.
String that indicates that something is left out or truncated.
How many existing messages shall be fetched after configuration.
if none of these flags are set, the default is chosen
Force NORMAL authorization, this is the default.
If this flag is set, automatic configuration is skipped.
Force OAuth2 authorization. This flag does not skip automatic configuration.
Before calling configure() with DC_LP_AUTH_OAUTH2 set,
the user has to confirm access at the URL returned by dc_get_oauth2_url().
How long a 1:1 chat canβt be used for sending while the SecureJoin is in progress. This should
be 10-20 seconds so that we are reasonably sure that the app remains active and receiving also
on mobile devices. See also
crate::chat::CantSendReason::SecurejoinWait
.
How far in the future the sender timestamp of a message is allowed to be, in seconds. Also used
in the group membership consistency algo to reject outdated membership changes.