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