mod_http_file_share: Add optional global quota on total storage usage Before, maximum storage usage (assuming all users upload as much as they could) would depend on the quota, retention period and number of users. Since number of users can vary, this makes it hard to know how much storage will be needed. Adding a limit to the total overall storage use solves this, making it simple to set it to some number based on what storage is actually available. Summary job run less often than the prune job since it touches the entire archive; and started before the prune job since it's needed before the first upload.

util.prosodyctl.check: Refuse to do ojn test unless prosody is running Other tests don't require a running prosody and I forgot to start it when testing.

prosodyctl: Add external connectivity check based on observe.jabber.network This uses the (experimental) observe.jabber.network API to perform external connectivity checks. The idea is to complement the checks prosodyctl can already do with a (nearly) complete s2s/c2s handshake from a remote party to test the entire stack.

mod_c2s: Rename Direct TLS listener 'c2s_direct_tls' for clarity And to follow existing naming practices better than 'legacy_ssl' did.

util.prosodyctl.check: Add TODO about replacements for deprecated settings

util.prosodyctl.check: Check for server-to-server Direct TLS records

mod_s2s: Rename Direct TLS listener 's2s_direct_tls' Following the style of other options like (c2s|s2s)_require_encryption, s2s_secure_auth etc.

mod_s2s: Add a Direct TLS listener Mirroring the c2s 'direct_tls'. Naming things is hard. direct_tls_s2s_ports = { 5269+1 }

mod_s2s: Handle connections having TLS from the start This could be done with multiplexing, or a future additional port definition.

mod_s2s: Factor out procedure for newly encrypted sessions Goal is to call this if the connection is using Direct TLS, either via multiplexing or a future Direct TLS S2S port.