Configuration#

Setting up a slidge component#

Refer to the slidge admin docs for generic instructions on how to set up a slidge component, and for slidge core configuration options.

API_HASH	Telegram app api_hash, obtained at https://my.telegram.org/apps If you dont set it, users will have to enter their own on registration.
API_ID	Telegram app api_id, obtained at https://my.telegram.org/apps If you dont set it, users will have to enter their own on registration.
ATTACHMENT_MAX_SIZE	Maximum file size (in bytes) to download from telegram automatically/
BIG_AVATARS	Fetch contact avatars in high-resolution (640x640) instead of the default 160x160. NB: slidge core main config AVATAR_SIZE still applies.
GROUP_HISTORY_MAXIMUM_MESSAGES	The number of messages to fetch from a group history. These messages and their attachments will be fetched on slidge startup.
MAX_PARALLEL_DOWNLOADS	Maximum number of parallel telegram downloads across all sessions.
OUTGOING_STICKERS_REGEXP	(workaround until the proper XEP is implemented) Set this to a regexp to treat certain attachments sent from the XMPP client as telegram custom stickers. Example: 'outgoing-stickers-regexp=.*\.webp' for webp images.
REGISTRATION_AUTH_CODE_TIMEOUT	On registration, users will be prompted for a 2FA code they receive on other telegram clients.
TDLIB_KEY	Key used to encrypt tdlib persistent DB
TDLIB_TIMEOUT	Timeout for telegram requests. If you get crashed related to timeout errors, you might want to increase that.
TDLIB_PATH	Defaults to ${SLIDGE_HOME_DIR}/tdlib