mod_http_oauth2: Advertise the currently supported id_token signing algorithm This field is REQUIRED. The algorithm RS256 MUST be included, but isn't because we don't implement it, as that would require implementing a pile of additional cryptography and JWT stuff. Instead the id_token is signed using the client secret, which allows verification by the client, since it's a shared secret per OpenID Connect Core 1.0 § 10.1 under Symmetric Signatures. OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that are not supported here, but that's okay because this is served from the RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!

# Groupchat 1.0 usage statistics gathering

Groupchat 1.0 was probably the protocol that predated
[XEP-0045: Multi-User Chat] and there is still some compatibility that
lives on, in the XEP and in implementations.

This module tries to detect clients still using the GC 1.0 protocol and
what software they run, to determine if support can be removed. 

Since joins in the GC 1.0 protocol are highly ambiguous, some hits
reported will be because of desynchronized MUC clients

# Compatibility

Should work with Prosody 0.10.x and earlier.

It will not work with current trunk, since the MUC code has had major
changes.