tileradotorg/mautrix-whatsapp
1
0
Fork 0
forked from MirrorHub/mautrix-whatsapp
Code Pull requests Activity

Move media request config and fix line wrapping

Browse source
This commit is contained in:
Tulir Asokan 2023-06-19 21:20:52 +03:00
parent c850f6f373
commit ccd43b2080
1 changed files with 26 additions and 35 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

61
example-config.yaml
View file

@ -148,27 +148,10 @@ bridge:
size_mb_limit: null size_mb_limit: null
# This is presumably the local storage quota, which may affect what the phone includes in the history sync blob. # This is presumably the local storage quota, which may affect what the phone includes in the history sync blob.
storage_quota_mb: null storage_quota_mb: null
# Settings for media requests. If the media expired, then it will not # If this value is greater than 0, then if the conversation's last message was more than
# be on the WA servers. # this number of hours ago, then the conversation will automatically be marked it as read.
# Media can always be requested by reacting with the ♻️ (recycle) emoji. # Conversations that have a last message that is less than this number of hours ago will
# These settings determine if the media requests should be done # have their unread status synced from WhatsApp.
# automatically during or after backfill.
media_requests:
# Should expired media be automatically requested from the server as
# part of the backfill process?
auto_request_media: true
# Whether to request the media immediately after the media message
# is backfilled ("immediate") or at a specific time of the day
# ("local_time").
request_method: immediate
# If request_method is "local_time", what time should the requests
# be sent (in minutes after midnight)?
request_local_time: 120
# If this value is greater than 0, then if the conversation's last
# message was more than this number of hours ago, then the conversation
# will automatically be marked it as read.
# Conversations that have a last message that is less than this number
# of hours ago will have their unread status synced from WhatsApp.
unread_hours_threshold: 0 unread_hours_threshold: 0
############################################################################### ###############################################################################
@ -176,24 +159,32 @@ bridge:
# which is no longer supported in Synapse. # # which is no longer supported in Synapse. #
############################################################################### ###############################################################################
# Settings for immediate backfills. These backfills should generally be # Settings for media requests. If the media expired, then it will not be on the WA servers.
# small and their main purpose is to populate each of the initial chats # Media can always be requested by reacting with the ♻️ (recycle) emoji.
# (as configured by max_initial_conversations) with a few messages so # These settings determine if the media requests should be done automatically during or after backfill.
# that you can continue conversations without loosing context. media_requests:
# Should expired media be automatically requested from the server as part of the backfill process?
auto_request_media: true
# Whether to request the media immediately after the media message is backfilled ("immediate")
# or at a specific time of the day ("local_time").
request_method: immediate
# If request_method is "local_time", what time should the requests be sent (in minutes after midnight)?
request_local_time: 120
# Settings for immediate backfills. These backfills should generally be small and their main purpose is
# to populate each of the initial chats (as configured by max_initial_conversations) with a few messages
# so that you can continue conversations without losing context.
immediate: immediate:
# The number of concurrent backfill workers to create for immediate # The number of concurrent backfill workers to create for immediate backfills.
# backfills. Note that using more than one worker could cause the # Note that using more than one worker could cause the room list to jump around
# room list to jump around since there are no guarantees about the # since there are no guarantees about the order in which the backfills will complete.
# order in which the backfills will complete.
worker_count: 1 worker_count: 1
# The maximum number of events to backfill initially. # The maximum number of events to backfill initially.
max_events: 10 max_events: 10
# Settings for deferred backfills. The purpose of these backfills are # Settings for deferred backfills. The purpose of these backfills are to fill in the rest of
# to fill in the rest of the chat history that was not covered by the # the chat history that was not covered by the immediate backfills.
# immediate backfills. These backfills generally should happen at a # These backfills generally should happen at a slower pace so as not to overload the homeserver.
# slower pace so as not to overload the homeserver. # Each deferred backfill config should define a "stage" of backfill (i.e. the last week of messages).
# Each deferred backfill config should define a "stage" of backfill # The fields are as follows:
# (i.e. the last week of messages). The fields are as follows:
# - start_days_ago: the number of days ago to start backfilling from. # - start_days_ago: the number of days ago to start backfilling from.
# To indicate the start of time, use -1. For example, for a week ago, use 7. # To indicate the start of time, use -1. For example, for a week ago, use 7.
# - max_batch_events: the number of events to send per batch. # - max_batch_events: the number of events to send per batch.