Mercurial > prosody-modules
view mod_muc_mam_markers/README.markdown @ 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 | a1fc677d0cc8 |
| children |
line wrap: on
line source
--- labels: - 'Stage-alpha' summary: Save received chat markers into MUC archives' ... Introduction ============ Chat markers (XEP-0333) specification states that markers _SHOULD_ be archived. This is already happening in one to one conversations in the personal archives but not in Group Chats. This module hooks the _muc-message-is-historic_ event to customize the `mod_muc_mam` behavior and have the chat markers archived. Usage ===== First copy the module to the prosody plugins directory. Then add "muc\_mam\_markers" to your `modules\_enabled` list in your MUC component's definition. No configuration options are available.