# You can replace the self-signed certificate that synapse
# autogenerates on launch with your own SSL certificate + key pair
# if you like.  Any required intermediary certificates can be
# appended after the primary certificate in hierarchical order.
tls_certificate_path: "/etc/matrix-synapse/homeserver.tls.crt"

I don't think this has happened since Synapse 1.0 or so. Pretty sure that message is from Debian, in -unstable.

# You can replace the self-signed certificate that synapse
# autogenerates on launch with your own SSL certificate + key pair
# if you like.  Any required intermediary certificates can be
# appended after the primary certificate in hierarchical order.
tls_certificate_path: "/etc/matrix-synapse/homeserver.tls.crt"

I don't think this has been autogenerated since Synapse 1.0 or so. Pretty sure that message is from Debian, in -unstable.

$ apt policy matrix-synapse
matrix-synapse:
  Installed: 1.9.0-1
  Candidate: 1.9.0-1
  Version table:
 *** 1.9.0-1 500
        500 http://ftp.fi.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Als Antwort auf @grin:grin.hu
Is 1.9 okay? I heard some complaints about "slow servers"

# Load the new-style messages config if it exists. Otherwise fall back
# to the old method.
if "rc_message" in config:
    self.rc_message = RateLimitConfig(
        config["rc_message"], defaults={"per_second": 0.2, "burst_count": 10.0}
    )
else:
    self.rc_message = RateLimitConfig(
        {
            "per_second": config.get("rc_messages_per_second", 0.2),
            "burst_count": config.get("rc_message_burst_count", 10.0),
        }
    )

I was wondering why I couldn't adjust the ratelimiting in config (nothing happened). Debian's configuration still uses the old form values. (I haven't tried new form yet.)