Mercurial > prosody-modules
view mod_muc_badge/README.markdown @ 5416:2393dbae51ed
mod_http_oauth2: Add option for specifying TTL of registered clients
Meant to simplify configuration, since TTL vs ignoring expiration is
expected to be the main thing one would want to configure.
Unsure what the implications of having unlimited lifetime of clients
are, given no way to revoke them currently, short of rotating the
signing secret.
On one hand, it would be annoying to have the client expire.
On the other hand, it is trivial to re-register it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 04 May 2023 18:41:33 +0200 |
parents | a646fcb45334 |
children |
line wrap: on
line source
--- depends: - 'mod\_http' - 'mod\_muc' provides: - http title: 'mod\_muc\_badge' --- # Introduction This module generates a badge for MUC rooms at a HTTP URL like `https://conference.example.com:5281/muc_badge/room@conference.example.org` containing the number of occupants. Inspiration : <https://opkode.com/blog/xmpp-chat-badge/> # Configuration Option Type Default ------------------ -------- -------------------------- `badge_count` string `"%d online"` `badge_template` string A SVG image (see source) The template must be valid XML. If it contains `{label}` then this is replaced by `badge_label`, similarly, `{count}` is substituted by `badge_count` with `%d` changed to the number of occupants. Details of the HTTP URL is determined by [standard Prosody HTTP server configuration][doc:http]. # Example ```lua Component "conference.example.com" "muc" modules_enabled = { "muc_badge" } ```