Mercurial > prosody-modules
view mod_http_pep_avatar/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 | 451514e2d369 |
children |
line wrap: on
line source
--- summary: Serve PEP avatars from HTTP --- # Introduction This module serves avatars from local users who have published [XEP-0084: User Avatar] via [PEP][doc:modules:mod_pep]. # Configuring Simply load the module. Avatars are then available at `http://<host>:5280/pep_avatar/<username>` modules_enabled = { ... "http_pep_avatar"; } # Access Users must [configure] their Avatar PEP nodes to be public, otherwise access is denied. # Compatibility ------- --------------- trunk Works 0.11 Works 0.10 Does not work ------- --------------- [configure]: https://xmpp.org/extensions/xep-0060.html#owner-configure