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: 'Support XEP-0334: Message Processing Hints for MUC messages'
...

Introduction
============

This module will check for MUC messages with XEP-0334 Message
Processing Hints tags to qualify those messages as "historic"
for later MAM archiving or not.

Usage
=====

First copy the module to the prosody plugins directory.

Then add "muc\_mam\_hints" to your modules\_enabled list in your MUC
component:

``` {.lua}
Component "conference.example.org" "muc"
modules_enabled = {
  "muc_mam",
  "muc_mam_hints",
}
```