Mercurial > prosody-modules
view mod_muc_ping/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 25 Apr 2023 18:09:08 +0200 |
| parents | 59bedf167910 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Obsolete' superseded_by: mod_muc summary: XEP-0410 Server Optimization (now supported by Prosody mod_muc) --- This module implements the [Server Optimization](https://xmpp.org/extensions/xep-0410.html#serveroptimization) part of [XEP-0410: MUC Self-Ping] # Usage The module is loaded on MUC components: ```lua Component "muc.example.com" "muc" modules_enabled = { "muc_ping"; } ``` # Configuration No options. # Compatibility It should work with Prosody up until 0.10.x. Prosody 0.11.x and trunk natively supports XEP-0410 so this module is **not** needed.