# vim:ft=yaml

## Server ##

# The domain name of the server, with optional explicit port.

# This is used by remote servers to connect to this server,

# e.g. matrix.org, localhost:8080, etc.

# This is also the last part of your UserID.

#

server_name: "opensuse.org"

# When running as a daemon, the file to store the pid in

#

pid_file: /var/lib/matrix-synapse/homeserver.pid

# The path to the web client which will be served at /_matrix/client/

# if 'webclient' is configured under the 'listeners' configuration.

#

#web_client_location: "/path/to/web/root"

# The public-facing base URL that clients use to access this HS

# (not including _matrix/...). This is the same URL a user would

# enter into the 'custom HS URL' field on their client. If you

# use synapse with a reverse proxy, this should be the URL to reach

# synapse via the proxy.

#

public_baseurl: https://matrix.opensuse.org/

# Set the soft limit on the number of file descriptors synapse can use

# Zero is used to indicate synapse should set the soft limit to the

# hard limit.

#

#soft_file_limit: 0

# Set to false to disable presence tracking on this homeserver.

#

#use_presence: false

# Whether to require authentication to retrieve profile data (avatars,

# display names) of other users through the client API. Defaults to

# 'false'. Note that profile data is also available via the federation

# API, so this setting is of limited value if federation is enabled on

# the server.

#

#require_auth_for_profile_requests: true

# Uncomment to require a user to share a room with another user in order

# to retrieve their profile information. Only checked on Client-Server

# requests. Profile requests from other servers should be checked by the

# requesting server. Defaults to 'false'.

#

#limit_profile_requests_to_users_who_share_rooms: true

# If set to 'true', removes the need for authentication to access the server's

# public rooms directory through the client API, meaning that anyone can

# query the room directory. Defaults to 'false'.

#

allow_public_rooms_without_auth: true

# If set to 'true', allows any other homeserver to fetch the server's public

# rooms directory via federation. Defaults to 'false'.

#

allow_public_rooms_over_federation: true

# The default room version for newly created rooms.

#

# Known room versions are listed here:

# https://matrix.org/docs/spec/#complete-list-of-room-versions

#

# For example, for room version 1, default_room_version should be set

# to "1".

#

#default_room_version: "5"

# The GC threshold parameters to pass to `gc.set_threshold`, if defined

#

#gc_thresholds: [700, 10, 10]

# Set the limit on the returned events in the timeline in the get

# and sync operations. The default value is -1, means no upper limit.

#

#filter_timeline_limit: 5000

# Whether room invites to users on this server should be blocked

# (except those sent by local server admins). The default is False.

#

#block_non_admin_invites: true

# Room searching

#

# If disabled, new messages will not be indexed for searching and users

# will receive errors when searching for messages. Defaults to enabled.

#

#enable_search: false

# Restrict federation to the following whitelist of domains.

# N.B. we recommend also firewalling your federation listener to limit

# inbound federation traffic as early as possible, rather than relying

# purely on this application-layer restriction.  If not specified, the

# default is to whitelist everything.

#

#federation_domain_whitelist:

#  - lon.example.com

#  - nyc.example.com

#  - syd.example.com

# Prevent federation requests from being sent to the following

# blacklist IP address CIDR ranges. If this option is not specified, or

# specified with an empty list, no ip range blacklist will be enforced.

#

# As of Synapse v1.4.0 this option also affects any outbound requests to identity

# servers provided by user input.

#

# (0.0.0.0 and :: are always blacklisted, whether or not they are explicitly

# listed here, since they correspond to unroutable addresses.)

#

federation_ip_range_blacklist:

  - '127.0.0.0/8'

  - '10.0.0.0/8'

  - '172.16.0.0/12'

  - '192.168.0.0/16'

  - '100.64.0.0/10'

  - '169.254.0.0/16'

  - '::1/128'

  - 'fe80::/64'

  - 'fc00::/7'

# List of ports that Synapse should listen on, their purpose and their

# configuration.

#

# Options for each listener include:

#

#   port: the TCP port to bind to

#

#   bind_addresses: a list of local addresses to listen on. The default is

#       'all local interfaces'.

#

#   type: the type of listener. Normally 'http', but other valid options are:

#       'manhole' (see docs/manhole.md),

#       'metrics' (see docs/metrics-howto.md),

#       'replication' (see docs/workers.md).

#

#   tls: set to true to enable TLS for this listener. Will use the TLS

#       key/cert specified in tls_private_key_path / tls_certificate_path.

#

#   x_forwarded: Only valid for an 'http' listener. Set to true to use the

#       X-Forwarded-For header as the client IP. Useful when Synapse is

#       behind a reverse-proxy.

#

#   resources: Only valid for an 'http' listener. A list of resources to host

#       on this port. Options for each resource are:

#

#       names: a list of names of HTTP resources. See below for a list of

#           valid resource names.

#

#       compress: set to true to enable HTTP comression for this resource.

#

#   additional_resources: Only valid for an 'http' listener. A map of

#        additional endpoints which should be loaded via dynamic modules.

#

# Valid resource names are:

#

#   client: the client-server API (/_matrix/client), and the synapse admin

#       API (/_synapse/admin). Also implies 'media' and 'static'.

#

#   consent: user consent forms (/_matrix/consent). See

#       docs/consent_tracking.md.

#

#   federation: the server-server API (/_matrix/federation). Also implies

#       'media', 'keys', 'openid'

#

#   keys: the key discovery API (/_matrix/keys).

#

#   media: the media API (/_matrix/media).

#

#   metrics: the metrics interface. See docs/metrics-howto.md.

#

#   openid: OpenID authentication.

#

#   replication: the HTTP replication API (/_synapse/replication). See

#       docs/workers.md.

#

#   static: static resources under synapse/static (/_matrix/static). (Mostly

#       useful for 'fallback authentication'.)

#

#   webclient: A web client. Requires web_client_location to be set.

#

listeners:

  # TLS-enabled listener: for when matrix traffic is sent directly to synapse.

  #

  # Disabled by default. To enable it, uncomment the following. (Note that you

  # will also need to give Synapse a TLS key and certificate: see the TLS section

  # below.)

  #

  #- port: 8448

  #  type: http

  #  tls: true

  #  resources:

  #    - names: [client, federation]

  # Unsecure HTTP listener: for when matrix traffic passes through a reverse proxy

  # that unwraps TLS.

  #

  # If you plan to use a reverse proxy, please see

  # https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.md.

  #

  - port: 8008

    tls: false

    type: http

    x_forwarded: true

    bind_addresses: ['::']

    resources:

      - names: [client]

        compress: true

      - names: [federation]

      - names: [metrics]

    # example additional_resources:

    #

    #additional_resources:

    #  "/_matrix/my/custom/endpoint":

    #    module: my_module.CustomRequestHandler

    #    config: {}

  # Turn on the twisted ssh manhole service on localhost on the given

  # port.

  #

  #- port: 9000

  #  bind_addresses: ['::1', '127.0.0.1']

  #  type: manhole

## Homeserver blocking ##

# How to reach the server admin, used in ResourceLimitError

#

admin_contact: 'mailto:admin@opensuse.org'

# Global blocking

#

#hs_disabled: false

#hs_disabled_message: 'Human readable reason for why the HS is blocked'

# Monthly Active User Blocking

#

# Used in cases where the admin or server owner wants to limit to the

# number of monthly active users.

#

# 'limit_usage_by_mau' disables/enables monthly active user blocking. When

# anabled and a limit is reached the server returns a 'ResourceLimitError'

# with error type Codes.RESOURCE_LIMIT_EXCEEDED

#

# 'max_mau_value' is the hard limit of monthly active users above which

# the server will start blocking user actions.

#

# 'mau_trial_days' is a means to add a grace period for active users. It

# means that users must be active for this number of days before they

# can be considered active and guards against the case where lots of users

# sign up in a short space of time never to return after their initial

# session.

#

# 'mau_limit_alerting' is a means of limiting client side alerting

# should the mau limit be reached. This is useful for small instances

# where the admin has 5 mau seats (say) for 5 specific people and no

# interest increasing the mau limit further. Defaults to True, which

# means that alerting is enabled

#

#limit_usage_by_mau: false

#max_mau_value: 50

#mau_trial_days: 2

#mau_limit_alerting: false

# If enabled, the metrics for the number of monthly active users will

# be populated, however no one will be limited. If limit_usage_by_mau

# is true, this is implied to be true.

#

#mau_stats_only: false

# Sometimes the server admin will want to ensure certain accounts are

# never blocked by mau checking. These accounts are specified here.

#

#mau_limit_reserved_threepids:

#  - medium: 'email'

#    address: 'reserved_user@example.com'

# Used by phonehome stats to group together related servers.

#server_context: context

# Resource-constrained homeserver Settings

#

# If limit_remote_rooms.enabled is True, the room complexity will be

# checked before a user joins a new remote room. If it is above

# limit_remote_rooms.complexity, it will disallow joining or

# instantly leave.

#

# limit_remote_rooms.complexity_error can be set to customise the text

# displayed to the user when a room above the complexity threshold has

# its join cancelled.

#

# Uncomment the below lines to enable:

#limit_remote_rooms:

#  enabled: true

#  complexity: 1.0

#  complexity_error: "This room is too complex."

# Whether to require a user to be in the room to add an alias to it.

# Defaults to 'true'.

#

#require_membership_for_aliases: false

# Whether to allow per-room membership profiles through the send of membership

# events with profile information that differ from the target's global profile.

# Defaults to 'true'.

#

#allow_per_room_profiles: false

# How long to keep redacted events in unredacted form in the database. After

# this period redacted events get replaced with their redacted form in the DB.

#

# Defaults to `7d`. Set to `null` to disable.

#

#redaction_retention_period: 28d

# How long to track users' last seen time and IPs in the database.

#

# Defaults to `28d`. Set to `null` to disable clearing out of old rows.

#

#user_ips_max_age: 14d

# Message retention policy at the server level.

#

# Room admins and mods can define a retention period for their rooms using the

# 'm.room.retention' state event, and server admins can cap this period by setting

# the 'allowed_lifetime_min' and 'allowed_lifetime_max' config options.

#

# If this feature is enabled, Synapse will regularly look for and purge events

# which are older than the room's maximum retention period. Synapse will also

# filter events received over federation so that events that should have been

# purged are ignored and not stored again.

#

retention:

  # The message retention policies feature is disabled by default. Uncomment the

  # following line to enable it.

  #

  #enabled: true

  # Default retention policy. If set, Synapse will apply it to rooms that lack the

  # 'm.room.retention' state event. Currently, the value of 'min_lifetime' doesn't

  # matter much because Synapse doesn't take it into account yet.

  #

  #default_policy:

  #  min_lifetime: 1d

  #  max_lifetime: 1y

  # Retention policy limits. If set, a user won't be able to send a

  # 'm.room.retention' event which features a 'min_lifetime' or a 'max_lifetime'

  # that's not within this range. This is especially useful in closed federations,

  # in which server admins can make sure every federating server applies the same

  # rules.

  #

  #allowed_lifetime_min: 1d

  #allowed_lifetime_max: 1y

  # Server admins can define the settings of the background jobs purging the

  # events which lifetime has expired under the 'purge_jobs' section.

  #

  # If no configuration is provided, a single job will be set up to delete expired

  # events in every room daily.

  #

  # Each job's configuration defines which range of message lifetimes the job

  # takes care of. For example, if 'shortest_max_lifetime' is '2d' and

  # 'longest_max_lifetime' is '3d', the job will handle purging expired events in

  # rooms whose state defines a 'max_lifetime' that's both higher than 2 days, and

  # lower than or equal to 3 days. Both the minimum and the maximum value of a

  # range are optional, e.g. a job with no 'shortest_max_lifetime' and a

  # 'longest_max_lifetime' of '3d' will handle every room with a retention policy

  # which 'max_lifetime' is lower than or equal to three days.

  #

  # The rationale for this per-job configuration is that some rooms might have a

  # retention policy with a low 'max_lifetime', where history needs to be purged

  # of outdated messages on a more frequent basis than for the rest of the rooms

  # (e.g. every 12h), but not want that purge to be performed by a job that's

  # iterating over every room it knows, which could be heavy on the server.

  #

  #purge_jobs:

  #  - shortest_max_lifetime: 1d

  #    longest_max_lifetime: 3d

  #    interval: 12h

  #  - shortest_max_lifetime: 3d

  #    longest_max_lifetime: 1y

  #    interval: 1d

## TLS ##

# PEM-encoded X509 certificate for TLS.

# This certificate, as of Synapse 1.0, will need to be a valid and verifiable

# certificate, signed by a recognised Certificate Authority.

#

# See 'ACME support' below to enable auto-provisioning this certificate via

# Let's Encrypt.

#

# If supplying your own, be sure to use a `.pem` file that includes the

# full certificate chain including any intermediate certificates (for

# instance, if using certbot, use `fullchain.pem` as your certificate,

# not `cert.pem`).

#

#tls_certificate_path: "/var/lib/matrix-synapse/opensuse.org.tls.crt"

# PEM-encoded private key for TLS

#

#tls_private_key_path: "/var/lib/matrix-synapse/opensuse.org.tls.key"

# Whether to verify TLS server certificates for outbound federation requests.

#

# Defaults to `true`. To disable certificate verification, uncomment the

# following line.

#

#federation_verify_certificates: false

# The minimum TLS version that will be used for outbound federation requests.

#

# Defaults to `1`. Configurable to `1`, `1.1`, `1.2`, or `1.3`. Note

# that setting this value higher than `1.2` will prevent federation to most

# of the public Matrix network: only configure it to `1.3` if you have an

# entirely private federation setup and you can ensure TLS 1.3 support.

#

#federation_client_minimum_tls_version: 1.2

# Skip federation certificate verification on the following whitelist

# of domains.

#

# This setting should only be used in very specific cases, such as

# federation over Tor hidden services and similar. For private networks

# of homeservers, you likely want to use a private CA instead.

#

# Only effective if federation_verify_certicates is `true`.

#

#federation_certificate_verification_whitelist:

#  - lon.example.com

#  - *.domain.com

#  - *.onion

# List of custom certificate authorities for federation traffic.

#

# This setting should only normally be used within a private network of

# homeservers.

#

# Note that this list will replace those that are provided by your

# operating environment. Certificates must be in PEM format.

#

#federation_custom_ca_list:

#  - myCA1.pem

#  - myCA2.pem

#  - myCA3.pem

# ACME support: This will configure Synapse to request a valid TLS certificate

# for your configured `server_name` via Let's Encrypt.

#

# Note that provisioning a certificate in this way requires port 80 to be

# routed to Synapse so that it can complete the http-01 ACME challenge.

# By default, if you enable ACME support, Synapse will attempt to listen on

# port 80 for incoming http-01 challenges - however, this will likely fail

# with 'Permission denied' or a similar error.

#

# There are a couple of potential solutions to this:

#

#  * If you already have an Apache, Nginx, or similar listening on port 80,

#    you can configure Synapse to use an alternate port, and have your web

#    server forward the requests. For example, assuming you set 'port: 8009'

#    below, on Apache, you would write:

#

#    ProxyPass /.well-known/acme-challenge http://localhost:8009/.well-known/acme-challenge

#

#  * Alternatively, you can use something like `authbind` to give Synapse

#    permission to listen on port 80.

#

acme:

    # ACME support is disabled by default. Set this to `true` and uncomment

    # tls_certificate_path and tls_private_key_path above to enable it.

    #

    #enabled: false

    # Endpoint to use to request certificates. If you only want to test,

    # use Let's Encrypt's staging url:

    #     https://acme-staging.api.letsencrypt.org/directory

    #

    #url: https://acme-v01.api.letsencrypt.org/directory

    # Port number to listen on for the HTTP-01 challenge. Change this if

    # you are forwarding connections through Apache/Nginx/etc.

    #

    #port: 80

    # Local addresses to listen on for incoming connections.

    # Again, you may want to change this if you are forwarding connections

    # through Apache/Nginx/etc.

    #

    #bind_addresses: ['::', '0.0.0.0']

    # How many days remaining on a certificate before it is renewed.

    #

    #reprovision_threshold: 30

    # The domain that the certificate should be for. Normally this

    # should be the same as your Matrix domain (i.e., 'server_name'), but,

    # by putting a file at 'https://<server_name>/.well-known/matrix/server',

    # you can delegate incoming traffic to another server. If you do that,

    # you should give the target of the delegation here.

    #

    # For example: if your 'server_name' is 'example.com', but

    # 'https://example.com/.well-known/matrix/server' delegates to

    # 'matrix.example.com', you should put 'matrix.example.com' here.

    #

    # If not set, defaults to your 'server_name'.

    #

    #domain: matrix.opensuse.org

    # file to use for the account key. This will be generated if it doesn't

    # exist.

    #

    # If unspecified, we will use CONFDIR/client.key.

    #

    #account_key_file: /etc/matrix-synapse/acme_account.key

# List of allowed TLS fingerprints for this server to publish along

# with the signing keys for this server. Other matrix servers that

# make HTTPS requests to this server will check that the TLS

# certificates returned by this server match one of the fingerprints.

#

# Synapse automatically adds the fingerprint of its own certificate

# to the list. So if federation traffic is handled directly by synapse

# then no modification to the list is required.

#

# If synapse is run behind a load balancer that handles the TLS then it

# will be necessary to add the fingerprints of the certificates used by

# the loadbalancers to this list if they are different to the one

# synapse is using.

#

# Homeservers are permitted to cache the list of TLS fingerprints

# returned in the key responses up to the "valid_until_ts" returned in

# key. It may be necessary to publish the fingerprints of a new

# certificate and wait until the "valid_until_ts" of the previous key

# responses have passed before deploying it.

#

# You can calculate a fingerprint from a given TLS listener via:

# openssl s_client -connect $host:$port < /dev/null 2> /dev/null |

#   openssl x509 -outform DER | openssl sha256 -binary | base64 | tr -d '='

# or by checking matrix.org/federationtester/api/report?server_name=$host

#

#tls_fingerprints: [{"sha256": "<base64_encoded_sha256_fingerprint>"}]

## Database ##

#database:

  # The database engine name

  #name: "sqlite3"

  # Arguments to pass to the engine

  #args:

    # Path to the database

    #database: "/var/lib/matrix-synapse/homeserver.db"

database:

    name: psycopg2

    args:

        user: {{ pillar['profile']['matrix']['database_user'] }}

        password: {{ pillar['postgres']['users']['matrix']['password'] }}

        database: {{ pillar['profile']['matrix']['database_name'] }}

        host: {{ pillar['profile']['matrix']['database_host'] }}

        cp_min: 5

        cp_max: 10

# Number of events to cache in memory.

#

#event_cache_size: 10K

## Logging ##

# A yaml python logging config file as described by

# https://docs.python.org/3.7/library/logging.config.html#configuration-dictionary-schema

#

log_config: "/etc/matrix-synapse/log.yaml"

## Ratelimiting ##

# Ratelimiting settings for client actions (registration, login, messaging).

#

# Each ratelimiting configuration is made of two parameters:

#   - per_second: number of requests a client can send per second.

#   - burst_count: number of requests a client can send before being throttled.

#

# Synapse currently uses the following configurations:

#   - one for messages that ratelimits sending based on the account the client

#     is using

#   - one for registration that ratelimits registration requests based on the

#     client's IP address.

#   - one for login that ratelimits login requests based on the client's IP

#     address.

#   - one for login that ratelimits login requests based on the account the

#     client is attempting to log into.

#   - one for login that ratelimits login requests based on the account the

#     client is attempting to log into, based on the amount of failed login

#     attempts for this account.

#   - one for ratelimiting redactions by room admins. If this is not explicitly

#     set then it uses the same ratelimiting as per rc_message. This is useful

#     to allow room admins to deal with abuse quickly.

#

# The defaults are as shown below.

#

#rc_message:

#  per_second: 0.2

#  burst_count: 10

#

#rc_registration:

#  per_second: 0.17

#  burst_count: 3

#

#rc_login:

#  address:

#    per_second: 0.17

#    burst_count: 3

#  account:

#    per_second: 0.17

#    burst_count: 3

#  failed_attempts:

#    per_second: 0.17

#    burst_count: 3

#

#rc_admin_redaction:

#  per_second: 1

#  burst_count: 50

# Ratelimiting settings for incoming federation

#

# The rc_federation configuration is made up of the following settings:

#   - window_size: window size in milliseconds

#   - sleep_limit: number of federation requests from a single server in

#     a window before the server will delay processing the request.

#   - sleep_delay: duration in milliseconds to delay processing events

#     from remote servers by if they go over the sleep limit.

#   - reject_limit: maximum number of concurrent federation requests

#     allowed from a single server

#   - concurrent: number of federation requests to concurrently process

#     from a single server

#

# The defaults are as shown below.

#

#rc_federation:

#  window_size: 1000

#  sleep_limit: 10

#  sleep_delay: 500

#  reject_limit: 50

#  concurrent: 3

# Target outgoing federation transaction frequency for sending read-receipts,

# per-room.

#

# If we end up trying to send out more read-receipts, they will get buffered up

# into fewer transactions.

#

#federation_rr_transactions_per_room_per_second: 50

## Media Store ##

# Enable the media store service in the Synapse master. Uncomment the

# following if you are using a separate media store worker.

#

#enable_media_repo: false

# Directory where uploaded images and attachments are stored.

#

media_store_path: "/data/matrix/media_store"

# Media storage providers allow media to be stored in different

# locations.

#

#media_storage_providers:

#  - module: file_system

#    # Whether to write new local files.

#    store_local: false

#    # Whether to write new remote media

#    store_remote: false

#    # Whether to block upload requests waiting for write to this

#    # provider to complete

#    store_synchronous: false

#    config:

#       directory: /mnt/some/other/directory

# The largest allowed upload size in bytes

#

#max_upload_size: 10M

# Maximum number of pixels that will be thumbnailed

#

#max_image_pixels: 32M

# Whether to generate new thumbnails on the fly to precisely match

# the resolution requested by the client. If true then whenever

# a new resolution is requested by the client the server will

# generate a new thumbnail. If false the server will pick a thumbnail

# from a precalculated list.

#

#dynamic_thumbnails: false

# List of thumbnails to precalculate when an image is uploaded.

#

#thumbnail_sizes:

#  - width: 32

#    height: 32

#    method: crop

#  - width: 96

#    height: 96

#    method: crop

#  - width: 320

#    height: 240

#    method: scale

#  - width: 640

#    height: 480

#    method: scale

#  - width: 800

#    height: 600

#    method: scale

# Is the preview URL API enabled?

#

# 'false' by default: uncomment the following to enable it (and specify a

# url_preview_ip_range_blacklist blacklist).

#

url_preview_enabled: true

# List of IP address CIDR ranges that the URL preview spider is denied

# from accessing.  There are no defaults: you must explicitly

# specify a list for URL previewing to work.  You should specify any

# internal services in your network that you do not want synapse to try

# to connect to, otherwise anyone in any Matrix room could cause your

# synapse to issue arbitrary GET requests to your internal services,

# causing serious security issues.

#

# (0.0.0.0 and :: are always blacklisted, whether or not they are explicitly

# listed here, since they correspond to unroutable addresses.)

#

# This must be specified if url_preview_enabled is set. It is recommended that

# you uncomment the following list as a starting point.

#

url_preview_ip_range_blacklist:

  - '127.0.0.0/8'

  - '10.0.0.0/8'

  - '172.16.0.0/12'

  - '192.168.0.0/16'

  - '100.64.0.0/10'

  - '169.254.0.0/16'

  - '::1/128'

  - 'fe80::/64'

  - 'fc00::/7'

# List of IP address CIDR ranges that the URL preview spider is allowed

# to access even if they are specified in url_preview_ip_range_blacklist.

# This is useful for specifying exceptions to wide-ranging blacklisted

# target IP ranges - e.g. for enabling URL previews for a specific private

# website only visible in your network.

#

#url_preview_ip_range_whitelist:

#   - '192.168.1.1'

# Optional list of URL matches that the URL preview spider is

# denied from accessing.  You should use url_preview_ip_range_blacklist

# in preference to this, otherwise someone could define a public DNS

# entry that points to a private IP address and circumvent the blacklist.

# This is more useful if you know there is an entire shape of URL that

# you know that will never want synapse to try to spider.

#

# Each list entry is a dictionary of url component attributes as returned

# by urlparse.urlsplit as applied to the absolute form of the URL.  See

# https://docs.python.org/2/library/urlparse.html#urlparse.urlsplit

# The values of the dictionary are treated as an filename match pattern

# applied to that component of URLs, unless they start with a ^ in which

# case they are treated as a regular expression match.  If all the

# specified component matches for a given list item succeed, the URL is

# blacklisted.

#

#url_preview_url_blacklist:

#  # blacklist any URL with a username in its URI

#  - username: '*'

#

#  # blacklist all *.google.com URLs

#  - netloc: 'google.com'

#  - netloc: '*.google.com'

#

#  # blacklist all plain HTTP URLs

#  - scheme: 'http'

#

#  # blacklist http(s)://www.acme.com/foo

#  - netloc: 'www.acme.com'

#    path: '/foo'

#

#  # blacklist any URL with a literal IPv4 address

#  - netloc: '^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$'

# The largest allowed URL preview spidering size in bytes

#

#max_spider_size: 10M

## Captcha ##

# See docs/CAPTCHA_SETUP for full details of configuring this.

# This homeserver's ReCAPTCHA public key.

#

#recaptcha_public_key: "YOUR_PUBLIC_KEY"

# This homeserver's ReCAPTCHA private key.

#

#recaptcha_private_key: "YOUR_PRIVATE_KEY"

# Enables ReCaptcha checks when registering, preventing signup

# unless a captcha is answered. Requires a valid ReCaptcha

# public/private key.

#

#enable_registration_captcha: false

# A secret key used to bypass the captcha test entirely.

#

#captcha_bypass_secret: "YOUR_SECRET_HERE"

# The API endpoint to use for verifying m.login.recaptcha responses.

#

#recaptcha_siteverify_api: "https://www.recaptcha.net/recaptcha/api/siteverify"

## TURN ##

# The public URIs of the TURN server to give to clients

#

#turn_uris: []

# The shared secret used to compute passwords for the TURN server

#

#turn_shared_secret: "YOUR_SHARED_SECRET"

# The Username and password if the TURN server needs them and

# does not use a token

#

#turn_username: "TURNSERVER_USERNAME"

#turn_password: "TURNSERVER_PASSWORD"

# How long generated TURN credentials last

#

#turn_user_lifetime: 1h

# Whether guests should be allowed to use the TURN server.

# This defaults to True, otherwise VoIP will be unreliable for guests.

# However, it does introduce a slight security risk as it allows users to

# connect to arbitrary endpoints without having first signed up for a

# valid account (e.g. by passing a CAPTCHA).

#

#turn_allow_guests: true

## Registration ##

#

# Registration can be rate-limited using the parameters in the "Ratelimiting"

# section of this file.

# Enable registration for new users.

#

enable_registration: false

# Optional account validity configuration. This allows for accounts to be denied