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