Mercurial > prosody-modules
view mod_ping_muc/README.md @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 21 Mar 2023 21:57:18 +0100 |
| parents | 0772facc786f |
| children | c094eabdb30f |
line wrap: on
line source
--- summary: Yet another MUC reliability module rockspec: dependencies: - mod_track_muc_joins labels: - Stage-Alpha ... This module reacts to [server-to-server][doc:s2s] connections closing by performing [XEP-0410: MUC Self-Ping] from the server side to check if users are still connected to MUCs they have joined according [mod_track_muc_joins]. If it can't be confirmed that the user is still joined then their client devices are notified about this allowing them to re-join. # Installing ``` prosodyctl install mod_ping_muc ``` # Configuring No configuration. Enable as a regular module in [`modules_enabled`][doc:modules_enabled] globally or under a `VirtualHost`: ```lua modules_enabled = { -- other modules etc "track_muc_joins", "ping_muc", } ``` # Compatibility Requires Prosody 0.12.x or trunk