mod_http_oauth2: Implement stateless dynamic client registration Replaces previous explicit registration that required either the additional module mod_adhoc_oauth2_client or manually editing the database. That method was enough to have something to test with, but would not probably not scale easily. Dynamic client registration allows creating clients on the fly, which may be even easier in theory. In order to not allow basically unauthenticated writes to the database, we implement a stateless model here. per_host_key := HMAC(config -> oauth2_registration_key, hostname) client_id := JWT { client metadata } signed with per_host_key client_secret := HMAC(per_host_key, client_id) This should ensure everything we need to know is part of the client_id, allowing redirects etc to be validated, and the client_secret can be validated with only the client_id and the per_host_key. A nonce injected into the client_id JWT should ensure nobody can submit the same client metadata and retrieve the same client_secret

---
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.