Raw YAML - Releases: latest, v26.08, v26.07
1# Network-specific config options
2network:
3 # Displayname template for FB/IG users. Available variables:
4 # .DisplayName - The display name set by the user.
5 # .Username - The username set by the user.
6 # .ID - The internal user ID of the user.
7 displayname_template: '{{or .DisplayName .Username "Unknown user"}}'
8
9 # Static proxy address (HTTP or SOCKS5) for connecting to Instagram.
10 proxy:
11 # HTTP endpoint to request new proxy address from, for dynamically assigned proxies.
12 # The endpoint must return a JSON body with a string field called proxy_url.
13 get_proxy_from:
14 # Should media be proxied too?
15 proxy_media: false
16 # Should other traffic, not configured here, be proxied?
17 proxy_other: true
18 # Minimum interval between full reconnects in seconds, default is 1 hour
19 min_full_reconnect_interval_seconds: 3600
20 # Interval to force refresh the connection (full reconnect), default is 20 hours. Set 0 to disable force refreshes.
21 force_refresh_interval_seconds: 72000
22 # Should connection state be cached to allow quicker restarts?
23 cache_connection_state: true
24 # Disable fetching XMA media (reels, stories, etc) when backfilling.
25 disable_xma_backfill: true
26 # Disable fetching XMA media entirely.
27 disable_xma_always: false
28 # Should typing notification bridging be disabled?
29 # Bridging typing notifications requires 2 extra connections per user (one for receiving and one for sending),
30 # because Meta only employs professional software engineers who make excellent architecture decisions.
31 disable_typing: false
32 # Should view-once messages be disabled entirely?
33 disable_view_once: false
34
35 # Thread backfill settings for syncing older conversations
36 thread_backfill:
37 # Number of batches (pages) to backfill (-1 for unlimited, 0 to disable)
38 batch_count: 0
39 # Delay between fetching each batch of threads (to avoid rate limiting)
40 batch_delay: 2s
41
42
43# Config options that affect the central bridge module.
44bridge:
45 # The prefix for commands. Only required in non-management rooms.
46 command_prefix: '!instagram'
47 # Should the bridge create a space for each login containing the rooms that account is in?
48 personal_filtering_spaces: true
49 # Whether the bridge should set names and avatars explicitly for DM portals.
50 # This is only necessary when using clients that don't support MSC4171.
51 private_chat_portal_meta: true
52 # Should events be handled asynchronously within portal rooms?
53 # If true, events may end up being out of order, but slow events won't block other ones.
54 # This is not yet safe to use.
55 async_events: false
56 # Should every user have their own portals rather than sharing them?
57 # By default, users who are in the same group on the remote network will be
58 # in the same Matrix room bridged to that group. If this is set to true,
59 # every user will get their own Matrix room instead.
60 # SETTING THIS IS IRREVERSIBLE AND POTENTIALLY DESTRUCTIVE IF PORTALS ALREADY EXIST.
61 split_portals: false
62 # Should the bridge resend `m.bridge` events to all portals on startup?
63 resend_bridge_info: false
64 # Should `m.bridge` events be sent without a state key?
65 # By default, the bridge uses a unique key that won't conflict with other bridges.
66 no_bridge_info_state_key: false
67 # Should bridge connection status be sent to the management room as `m.notice` events?
68 # These contain the same data that can be posted to an external HTTP server using homeserver -> status_endpoint.
69 # Allowed values: none, errors, all
70 bridge_status_notices: errors
71 # How long after an unknown error should the bridge attempt a full reconnect?
72 # Must be at least 1 minute. The bridge will add an extra ±20% jitter to this value.
73 unknown_error_auto_reconnect: null
74 # Maximum number of times to do the auto-reconnect above.
75 # The counter is per login, but is never reset except on logout and restart.
76 unknown_error_max_auto_reconnects: 10
77
78 # Should leaving Matrix rooms be bridged as leaving groups on the remote network?
79 bridge_matrix_leave: false
80 # Should `m.notice` messages be bridged?
81 bridge_notices: false
82 # Should room tags only be synced when creating the portal? Tags mean things like favorite/pin and archive/low priority.
83 # Tags currently can't be synced back to the remote network, so a continuous sync means tagging from Matrix will be undone.
84 tag_only_on_create: true
85 # List of tags to allow bridging. If empty, no tags will be bridged.
86 only_bridge_tags: [m.favourite, m.lowpriority]
87 # Should room mute status only be synced when creating the portal?
88 # Like tags, mutes can't currently be synced back to the remote network.
89 mute_only_on_create: true
90 # Should the bridge check the db to ensure that incoming events haven't been handled before
91 deduplicate_matrix_messages: false
92 # Should cross-room reply metadata be bridged?
93 # Most Matrix clients don't support this and servers may reject such messages too.
94 cross_room_replies: false
95 # If a state event fails to bridge, should the bridge revert any state changes made by that event?
96 revert_failed_state_changes: false
97 # In portals with no relay set, should Matrix users be kicked if they're
98 # not logged into an account that's in the remote chat?
99 kick_matrix_users: true
100 # Should the bridge listen to com.beeper.state_request events?
101 # This is not necessary for anything outside of Beeper.
102 enable_send_state_requests: false
103 # Should the com.beeper.bridge.identifiers list in global ghost profiles include phone numbers?
104 phone_numbers_in_profile: false
105
106 # What should be done to portal rooms when a user logs out or is logged out?
107 # Permitted values:
108 # nothing - Do nothing, let the user stay in the portals
109 # kick - Remove the user from the portal rooms, but don't delete them
110 # unbridge - Remove all ghosts in the room and disassociate it from the remote chat
111 # delete - Remove all ghosts and users from the room (i.e. delete it)
112 cleanup_on_logout:
113 # Should cleanup on logout be enabled at all?
114 enabled: false
115 # Settings for manual logouts (explicitly initiated by the Matrix user)
116 manual:
117 # Action for private portals which will never be shared with other Matrix users.
118 private: nothing
119 # Action for portals with a relay user configured.
120 relayed: nothing
121 # Action for portals which may be shared, but don't currently have any other Matrix users.
122 shared_no_users: nothing
123 # Action for portals which have other logged-in Matrix users.
124 shared_has_users: nothing
125 # Settings for credentials being invalidated (initiated by the remote network, possibly through user action).
126 # Keys have the same meanings as in the manual section.
127 bad_credentials:
128 private: nothing
129 relayed: nothing
130 shared_no_users: nothing
131 shared_has_users: nothing
132
133 # Settings for relay mode
134 relay:
135 # Whether relay mode should be allowed. If allowed, the set-relay command can be used to turn any
136 # authenticated user into a relaybot for that chat.
137 enabled: false
138 # Should only admins be allowed to set themselves as relay users?
139 # If true, non-admins can only set users listed in default_relays as relays in a room.
140 admin_only: true
141 # Should default relays be preferred when an explicit login ID isn't specified even if the user is logged in?
142 # This applies to the set-relay and bridge commands sent by any user, including admins.
143 prefer_default: true
144 # Should non-admins be allowed to use the bridge and sync-chat commands via default relays specified below?
145 allow_bridge: true
146 # List of user login IDs which anyone can set as a relay, as long as the relay user is in the room.
147 default_relays: []
148 # The formats to use when sending messages via the relaybot.
149 # Available variables:
150 # .Sender.UserID - The Matrix user ID of the sender.
151 # .Sender.Displayname - The display name of the sender (if set).
152 # .Sender.RequiresDisambiguation - Whether the sender's name may be confused with the name of another user in the room.
153 # .Sender.DisambiguatedName - The disambiguated name of the sender. This will be the displayname if set,
154 # plus the user ID in parentheses if the displayname is not unique.
155 # If the displayname is not set, this is just the user ID.
156 # .Message - The `formatted_body` field of the message.
157 # .Caption - The `formatted_body` field of the message, if it's a caption. Otherwise an empty string.
158 # .FileName - The name of the file being sent.
159 message_formats:
160 m.text: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
161 m.notice: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
162 m.emote: "* <b>{{ .Sender.DisambiguatedName }}</b> {{ .Message }}"
163 m.file: "<b>{{ .Sender.DisambiguatedName }}</b> sent a file{{ if .Caption }}: {{ .Caption }}{{ end }}"
164 m.image: "<b>{{ .Sender.DisambiguatedName }}</b> sent an image{{ if .Caption }}: {{ .Caption }}{{ end }}"
165 m.audio: "<b>{{ .Sender.DisambiguatedName }}</b> sent an audio file{{ if .Caption }}: {{ .Caption }}{{ end }}"
166 m.video: "<b>{{ .Sender.DisambiguatedName }}</b> sent a video{{ if .Caption }}: {{ .Caption }}{{ end }}"
167 m.location: "<b>{{ .Sender.DisambiguatedName }}</b> sent a location{{ if .Caption }}: {{ .Caption }}{{ end }}"
168 # For networks that support per-message displaynames (i.e. Slack and Discord), the template for those names.
169 # This has all the Sender variables available under message_formats (but without the .Sender prefix).
170 # Note that you need to manually remove the displayname from message_formats above.
171 displayname_format: "{{ .DisambiguatedName }}"
172
173 # Filter for automatically creating portals.
174 portal_create_filter:
175 # The mode for filtering, either `deny` or `allow`
176 mode: deny
177 # The list of portal IDs to deny or allow depending on the mode config.
178 # Items here can either be the plain portal ID as a string, or an object with `id` and `receiver` fields.
179 # The receiver field is necessary if you want to target a specific DM portal for example.
180 list: []
181 # A list of user login IDs from which to always deny creating portals.
182 # This is meant to be used with default relays, such that the relay bot
183 # being added to a group wouldn't automatically trigger portal creation.
184 always_deny_from_login: []
185
186 # Permissions for using the bridge.
187 # Permitted values:
188 # relay - Talk through the relaybot (if enabled), no access otherwise
189 # commands - Access to use commands in the bridge, but not login.
190 # user - Access to use the bridge with puppeting.
191 # admin - Full access, user level with some additional administration tools.
192 # Permitted keys:
193 # * - All Matrix users
194 # domain - All users on that homeserver
195 # mxid - Specific user
196 permissions:
197 "*": relay
198 "example.com": user
199 "@admin:example.com": admin
200
201# Config for the bridge's database.
202database:
203 # The database type. "sqlite3-fk-wal" and "postgres" are supported.
204 type: postgres
205 # The database URI.
206 # SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
207 # https://github.com/mattn/go-sqlite3#connection-string
208 # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
209 # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
210 uri: postgres://user:password@host/database?sslmode=disable
211 # Maximum number of connections.
212 max_open_conns: 5
213 max_idle_conns: 1
214 # Maximum connection idle time and lifetime before they're closed. Disabled if null.
215 # Parsed with https://pkg.go.dev/time#ParseDuration
216 max_conn_idle_time: null
217 max_conn_lifetime: null
218
219# Homeserver details.
220homeserver:
221 # The address that this appservice can use to connect to the homeserver.
222 # Local addresses without HTTPS are generally recommended when the bridge is running on the same machine,
223 # but https also works if they run on different machines.
224 address: http://example.localhost:8008
225 # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
226 domain: example.com
227
228 # What software is the homeserver running?
229 # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
230 software: standard
231 # The URL to push real-time bridge status to.
232 # If set, the bridge will make POST requests to this URL whenever a user's remote network connection state changes.
233 # The bridge will use the appservice as_token to authorize requests.
234 status_endpoint:
235 # Endpoint for reporting per-message status.
236 # If set, the bridge will make POST requests to this URL when processing a message from Matrix.
237 # It will make one request when receiving the message (step BRIDGE), one after decrypting if applicable
238 # (step DECRYPTED) and one after sending to the remote network (step REMOTE). Errors will also be reported.
239 # The bridge will use the appservice as_token to authorize requests.
240 message_send_checkpoint_endpoint:
241 # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
242 async_media: false
243
244 # Should the bridge use a websocket for connecting to the homeserver?
245 # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy,
246 # mautrix-asmux (deprecated), and hungryserv (proprietary).
247 websocket: false
248 # How often should the websocket be pinged? Pinging will be disabled if this is zero.
249 ping_interval_seconds: 0
250 # When requests to the homeserver fail with a 502/503/504/429 status or a network error,
251 # how many times should the bridge retry the request before giving up?
252 retry_limit: 4
253
254# Application service host/registration related details.
255# Changing these values requires regeneration of the registration (except when noted otherwise)
256appservice:
257 # The address that the homeserver can use to connect to this appservice.
258 # Like the homeserver address, a local non-https address is recommended when the bridge is on the same machine.
259 # If the bridge is elsewhere, you must secure the connection yourself (e.g. with https or wireguard)
260 # If you want to use https, you need to use a reverse proxy. The bridge does not have TLS support built in.
261 address: http://localhost:29330
262 # A public address that external services can use to reach this appservice.
263 # This is only needed for things like public media. A reverse proxy is generally necessary when using this field.
264 # This value doesn't affect the registration file.
265 public_address: https://bridge.example.com
266
267 # The hostname and port where this appservice should listen.
268 # For Docker, you generally have to change the hostname to 0.0.0.0.
269 hostname: 127.0.0.1
270 port: 29330
271
272 # The unique ID of this appservice.
273 id: instagram
274 # Appservice bot details.
275 bot:
276 # Username of the appservice bot.
277 username: instagrambot
278 # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
279 # to leave display name/avatar as-is.
280 displayname: Instagram bridge bot
281 avatar: mxc://maunium.net/JxjlbZUlCPULEeHZSwleUXQv
282
283 # Whether to receive ephemeral events via appservice transactions.
284 ephemeral_events: true
285 # Should incoming events be handled asynchronously?
286 # This may be necessary for large public instances with lots of messages going through.
287 # However, messages will not be guaranteed to be bridged in the same order they were sent in.
288 # This value doesn't affect the registration file.
289 async_transactions: false
290
291 # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
292 as_token: "This value is generated when generating the registration"
293 hs_token: "This value is generated when generating the registration"
294
295 # Localpart template of MXIDs for remote users.
296 # {{.}} is replaced with the internal ID of the user.
297 username_template: instagram_{{.}}
298
299# Config options that affect the Matrix connector of the bridge.
300matrix:
301 # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
302 message_status_events: false
303 # Whether the bridge should send a read receipt after successfully bridging a message.
304 delivery_receipts: false
305 # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
306 message_error_notices: true
307 # Whether the bridge should update the m.direct account data event when double puppeting is enabled.
308 sync_direct_chat_list: true
309 # Whether created rooms should have federation enabled. If false, created portal rooms
310 # will never be federated. Changing this option requires recreating rooms.
311 federate_rooms: true
312 # The threshold as bytes after which the bridge should roundtrip uploads via the disk
313 # rather than keeping the whole file in memory.
314 upload_file_threshold: 5242880
315 # Should the bridge set additional custom profile info for ghosts?
316 # This can make a lot of requests, as there's no batch profile update endpoint.
317 ghost_extra_profile_info: false
318
319# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors.
320analytics:
321 # API key to send with tracking requests. Tracking is disabled if this is null.
322 token: null
323 # Address to send tracking requests to.
324 url: https://api.segment.io/v1/track
325 # Optional user ID for tracking events. If null, defaults to using Matrix user ID.
326 user_id: null
327
328# Settings for provisioning API
329provisioning:
330 # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
331 # or if set to "disable", the provisioning API will be disabled. Must be at least 16 characters.
332 shared_secret: generate
333 # Whether to allow provisioning API requests to be authed using Matrix access tokens.
334 # This follows the same rules as double puppeting to determine which server to contact to check the token,
335 # which means that by default, it only works for users on the same server as the bridge.
336 allow_matrix_auth: true
337 # Enable debug API at /debug with provisioning authentication.
338 debug_endpoints: false
339 # Enable session transfers between bridges. Note that this only validates Matrix or shared secret
340 # auth before passing live network client credentials down in the response.
341 enable_session_transfers: false
342 # Should the provisioning API fail immediately if a webauthn step is returned?
343 # This is mostly useful for clients that don't yet support it and want a trackable error instead.
344 fail_on_webauthn: false
345
346# Some networks require publicly accessible media download links (e.g. for user avatars when using Discord webhooks).
347# These settings control whether the bridge will provide such public media access.
348public_media:
349 # Should public media be enabled at all?
350 # The public_address field under the appservice section MUST be set when enabling public media.
351 enabled: false
352 # A key for signing public media URLs.
353 # If set to "generate", a random key will be generated.
354 signing_key: generate
355 # Number of seconds that public media URLs are valid for.
356 # If set to 0, URLs will never expire.
357 expiry: 0
358 # Length of hash to use for public media URLs. Must be between 0 and 32.
359 hash_length: 32
360 # The path prefix for generated URLs. Note that this will NOT change the path where media is actually served.
361 # If you change this, you must configure your reverse proxy to rewrite the path accordingly.
362 path_prefix: /_mautrix/publicmedia
363 # Should the bridge store media metadata in the database in order to support encrypted media and generate shorter URLs?
364 # If false, the generated URLs will just have the MXC URI and a HMAC signature.
365 # The hash_length field will be used to decide the length of the generated URL.
366 # This also allows invalidating URLs by deleting the database entry.
367 use_database: false
368
369# Settings for converting remote media to custom mxc:// URIs instead of reuploading.
370# More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html
371direct_media:
372 # Should custom mxc:// URIs be used instead of reuploading media?
373 enabled: false
374 # The server name to use for the custom mxc:// URIs.
375 # This server name will effectively be a real Matrix server, it just won't implement anything other than media.
376 # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge.
377 server_name: discord-media.example.com
378 # Optionally a custom .well-known response. This defaults to `server_name:443`
379 well_known_response:
380 # Optionally specify a custom prefix for the media ID part of the MXC URI.
381 media_id_prefix:
382 # If the remote network supports media downloads over HTTP, then the bridge will use MSC3860/MSC3916
383 # media download redirects if the requester supports it. Optionally, you can force redirects
384 # and not allow proxying at all by setting this to false.
385 # This option does nothing if the remote network does not support media downloads over HTTP.
386 allow_proxy: true
387 # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
388 # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
389 server_key: generate
390
391# Settings for backfilling messages.
392# Note that the exact way settings are applied depends on the network connector.
393# See https://docs.mau.fi/bridges/general/backfill.html for more details.
394backfill:
395 # Whether to do backfilling at all.
396 enabled: false
397 # Maximum number of messages to backfill in empty rooms.
398 # If this is zero or negative, backfill will be disabled in new rooms.
399 max_initial_messages: 50
400 # Maximum number of missed messages to backfill after bridge restarts.
401 max_catchup_messages: 500
402 # If a backfilled chat is older than this number of hours,
403 # mark it as read even if it's unread on the remote network.
404 unread_hours_threshold: 720
405 # Settings for backfilling threads within other backfills.
406 threads:
407 # Maximum number of messages to backfill in a new thread.
408 max_initial_messages: 50
409 # Settings for the backwards backfill queue. This only applies when connecting to
410 # Beeper as standard Matrix servers don't support inserting messages into history.
411 queue:
412 # Should the backfill queue be enabled?
413 enabled: false
414 # Should manual calls to backfill queue tasks be allowed?
415 manual: false
416 # Number of messages to backfill in one batch.
417 batch_size: 100
418 # Delay between batches in seconds.
419 batch_delay: 20
420 # Maximum number of batches to backfill per portal.
421 # If set to -1, all available messages will be backfilled.
422 max_batches: -1
423 # Optional network-specific overrides for max batches.
424 # Interpretation of this field depends on the network connector.
425 max_batches_override: {}
426
427# Settings for enabling double puppeting
428double_puppet:
429 # Servers to always allow double puppeting from.
430 # This is only for other servers and should NOT contain the server the bridge is on.
431 servers:
432 anotherserver.example.org: https://matrix.anotherserver.example.org
433 # Whether to allow client API URL discovery for other servers. When using this option,
434 # users on other servers can use double puppeting even if their server URLs aren't
435 # explicitly added to the servers map above.
436 allow_discovery: false
437 # Shared secrets for automatic double puppeting.
438 # See https://docs.mau.fi/bridges/general/double-puppeting.html for instructions.
439 secrets:
440 example.com: as_token:foobar
441
442# End-to-bridge encryption support options.
443#
444# See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
445encryption:
446 # Whether to enable encryption at all. If false, the bridge will not function in encrypted rooms.
447 allow: false
448 # Whether to force-enable encryption in all bridged rooms.
449 default: false
450 # Whether to require all messages to be encrypted and drop any unencrypted messages.
451 require: false
452 # Whether to use MSC3202/MSC4203 instead of /sync long polling for receiving encryption-related data.
453 # This is an experimental option, see the docs for more info.
454 # Changing this option requires updating the appservice registration file.
455 appservice: false
456 # Whether to use MSC4190 instead of appservice login to create the bridge bot device.
457 # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202.
458 # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861).
459 msc4190: false
460 # Whether to encrypt reactions and reply metadata as per MSC4392.
461 # This is not supported by most clients.
462 msc4392: false
463 # Should the bridge bot generate a recovery key and cross-signing keys and verify itself?
464 # Note that without the latest version of MSC4190, this will fail if you reset the bridge database.
465 # The generated recovery key will be saved in the kv_store table under `recovery_key`.
466 self_sign: false
467 # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
468 # You must use a client that supports requesting keys from other users to use this feature.
469 allow_key_sharing: true
470 # Should m.mentions be sent in the unencrypted content? This is non-standard and should not be enabled.
471 plaintext_mentions: false
472 # Pickle key for encrypting encryption keys in the bridge database.
473 # If set to generate, a random key will be generated.
474 pickle_key: generate
475 # Options for deleting megolm sessions from the bridge.
476 delete_keys:
477 # Beeper-specific: delete outbound sessions when hungryserv confirms
478 # that the user has uploaded the key to key backup.
479 delete_outbound_on_ack: false
480 # Don't store outbound sessions in the inbound table.
481 dont_store_outbound: false
482 # Ratchet megolm sessions forward after decrypting messages.
483 ratchet_on_decrypt: false
484 # Delete fully used keys (index >= max_messages) after decrypting messages.
485 delete_fully_used_on_decrypt: false
486 # Delete previous megolm sessions from same device when receiving a new one.
487 delete_prev_on_new_session: false
488 # Delete megolm sessions received from a device when the device is deleted.
489 delete_on_device_delete: false
490 # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
491 periodically_delete_expired: false
492 # Delete inbound megolm sessions that don't have the received_at field used for
493 # automatic ratcheting and expired session deletion. This is meant as a migration
494 # to delete old keys prior to the bridge update.
495 delete_outdated_inbound: false
496 # What level of device verification should be required from users?
497 #
498 # Valid levels:
499 # unverified - Send keys to all device in the room.
500 # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
501 # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
502 # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
503 # Note that creating user signatures from the bridge bot is not currently possible.
504 # verified - Require manual per-device verification
505 # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
506 verification_levels:
507 # Minimum level for which the bridge should send keys to when bridging messages from the remote network to Matrix.
508 receive: unverified
509 # Minimum level that the bridge should accept for incoming Matrix messages.
510 send: unverified
511 # Minimum level that the bridge should require for accepting key requests.
512 share: cross-signed-tofu
513 # Options for Megolm room key rotation. These options allow you to configure the m.room.encryption event content.
514 # See https://spec.matrix.org/v1.10/client-server-api/#mroomencryption for more information about that event.
515 rotation:
516 # Enable custom Megolm room key rotation settings. Note that these
517 # settings will only apply to rooms created after this option is set.
518 enable_custom: false
519 # The maximum number of milliseconds a session should be used
520 # before changing it. The Matrix spec recommends 604800000 (a week)
521 # as the default.
522 milliseconds: 604800000
523 # The maximum number of messages that should be sent with a given a
524 # session before changing it. The Matrix spec recommends 100 as the
525 # default.
526 messages: 100
527 # Disable rotating keys when a user's devices change?
528 # You should not enable this option unless you understand all the implications.
529 disable_device_change_key_rotation: false
530
531# Prefix for environment variables. All variables with this prefix must map to valid config fields.
532# Nesting in variable names is represented with a dot (.).
533# If there are no dots in the name, two underscores (__) are replaced with a dot.
534#
535# e.g. if the prefix is set to `BRIDGE_`, then `BRIDGE_APPSERVICE__AS_TOKEN` will set appservice.as_token.
536# `BRIDGE_appservice.as_token` would work as well, but can't be set in a shell as easily.
537#
538# The variable names can also have a `_FILE` suffix to tell the bridge to read the value from the
539# path set in the variable rather than using the value directly.
540#
541# If this is null, reading config fields from environment will be disabled.
542env_config_prefix: null
543
544# Logging config. See https://github.com/tulir/zeroconfig for details.
545logging:
546 min_level: debug
547 writers:
548 - type: stdout
549 format: pretty-colored
550 - type: file
551 format: json
552 filename: ./logs/bridge.log
553 max_size: 100
554 max_backups: 10
555 compress: false