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