|
|
|
@@ -5,6 +5,9 @@ homeserver: |
|
|
|
address: {{ matrix_mautrix_whatsapp_homeserver_address }} |
|
|
|
# The domain of the homeserver (for MXIDs, etc). |
|
|
|
domain: {{ matrix_mautrix_whatsapp_homeserver_domain }} |
|
|
|
# What software is the homeserver running? |
|
|
|
# Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here. |
|
|
|
software: standard |
|
|
|
# The URL to push real-time bridge status to. |
|
|
|
# If set, the bridge will make POST requests to this URL whenever a user's whatsapp connection state changes. |
|
|
|
# The bridge will use the appservice as_token to authorize requests. |
|
|
|
@@ -52,7 +55,7 @@ appservice: |
|
|
|
# Whether or not to receive ephemeral events via appservice transactions. |
|
|
|
# Requires MSC2409 support (i.e. Synapse 1.22+). |
|
|
|
# You should disable bridge -> sync_with_custom_puppets when this is enabled. |
|
|
|
ephemeral_events: false |
|
|
|
ephemeral_events: true |
|
|
|
|
|
|
|
# Authentication tokens for AS <-> HS communication. Autogenerated; do not modify. |
|
|
|
as_token: "{{ matrix_mautrix_whatsapp_appservice_token }}" |
|
|
|
@@ -188,7 +191,7 @@ bridge: |
|
|
|
# Should Matrix users leaving groups be bridged to WhatsApp? |
|
|
|
bridge_matrix_leave: true |
|
|
|
# Should the bridge sync with double puppeting to receive EDUs that aren't normally sent to appservices. |
|
|
|
sync_with_custom_puppets: true |
|
|
|
sync_with_custom_puppets: false |
|
|
|
# Should the bridge update the m.direct account data event when double puppeting is enabled. |
|
|
|
# Note that updating the m.direct event is not atomic (except with mautrix-asmux) |
|
|
|
# and is therefore prone to race conditions. |
|
|
|
@@ -268,6 +271,9 @@ bridge: |
|
|
|
# Should the bridge never send alerts to the bridge management room? |
|
|
|
# These are mostly things like the user being logged out. |
|
|
|
disable_bridge_alerts: false |
|
|
|
# Should the bridge stop if the WhatsApp server says another user connected with the same session? |
|
|
|
# This is only safe on single-user bridges. |
|
|
|
crash_on_stream_replaced: false |
|
|
|
# Should the bridge detect URLs in outgoing messages, ask the homeserver to generate a preview, |
|
|
|
# and send it to WhatsApp? URL previews can always be sent using the `com.beeper.linkpreviews` |
|
|
|
# key in the event content even if this is disabled. |
|
|
|
@@ -311,6 +317,8 @@ bridge: |
|
|
|
# This will cause the bridge bot to be in private chats for the encryption to work properly. |
|
|
|
# It is recommended to also set private_chat_portal_meta to true when using this. |
|
|
|
default: {{ matrix_mautrix_whatsapp_bridge_encryption_default|to_json }} |
|
|
|
# Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data. |
|
|
|
appservice: false |
|
|
|
# Require encryption, drop any unencrypted messages. |
|
|
|
require: false |
|
|
|
# Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled. |
|
|
|
|