~xenrox/ansible

2c3d84ab8928f4198b24dd3609dceff62be7e67b — Thorben Günther 1 year, 9 months ago f0ca44d
matrix: Update mautrix-whatsapp config

0.5.0 release.
1 files changed, 20 insertions(+), 8 deletions(-)

M roles/matrix/templates/mautrix-whatsapp.yaml.j2
M roles/matrix/templates/mautrix-whatsapp.yaml.j2 => roles/matrix/templates/mautrix-whatsapp.yaml.j2 +20 -8
@@ 43,14 43,6 @@ appservice:
        max_conn_idle_time: null
        max_conn_lifetime: null

    # Settings for provisioning API
    provisioning:
        # Prefix for the provisioning API paths.
        prefix: /_matrix/provision
        # Shared secret for authentication. If set to "generate", a random secret will be generated,
        # or if set to "disable", the provisioning API will be disabled.
        shared_secret: {{ matrix_secrets['whatsapp_shared_secret'] }}

    # The unique ID of this appservice.
    id: whatsapp
    # Appservice bot details.


@@ 108,6 100,10 @@ bridge:
    personal_filtering_spaces: true
    # Should the bridge send a read receipt from the bridge bot when a message has been sent to WhatsApp?
    delivery_receipts: false
    # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
    message_status_events: false
    # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
    message_error_notices: true
    # Should incoming calls send a message to the Matrix room?
    call_start_notices: true
    # Should another user's cryptographic identity changing send a message to Matrix?


@@ 201,6 197,11 @@ bridge:
    # Note that updating the m.direct event is not atomic (except with mautrix-asmux)
    # and is therefore prone to race conditions.
    sync_direct_chat_list: false
    # Should the bridge use MSC2867 to bridge manual "mark as unread"s from
    # WhatsApp and set the unread status on initial backfill?
    # This will only work on clients that support the m.marked_unread or
    # com.famedly.marked_unread room account data.
    sync_manual_marked_unread: true
    # When double puppeting is enabled, users can use `!wa toggle` to change whether
    # presence and read receipts are bridged. These settings set the default values.
    # Existing users won't be affected when these are changed.


@@ 247,6 248,9 @@ bridge:
    # Should WhatsApp status messages be bridged into a Matrix room?
    # Disabling this won't affect already created status broadcast rooms.
    enable_status_broadcast: true
    # Should sending WhatsApp status messages be allowed?
    # This can cause issues if the user has lots of contacts, so it's disabled by default.
    disable_status_broadcast_send: true
    # Should the status broadcast room be muted and moved into low priority by default?
    # This is only applied when creating the room, the user can unmute it later.
    mute_status_broadcast: true


@@ 311,6 315,14 @@ bridge:
            # Verification by the bridge is not yet implemented.
            require_verification: true

    # Settings for provisioning API
    provisioning:
        # Prefix for the provisioning API paths.
        prefix: /_matrix/provision
        # Shared secret for authentication. If set to "generate", a random secret will be generated,
        # or if set to "disable", the provisioning API will be disabled.
        shared_secret: {{ matrix_secrets['whatsapp_shared_secret'] }}

    # Permissions for using the bridge.
    # Permitted values:
    #    relay - Talk through the relaybot (if enabled), no access otherwise