Mercurial > prosody-modules
view mod_muc_gc10/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 21 Mar 2023 21:57:18 +0100 |
| parents | 0167a102ed35 |
| children |
line wrap: on
line source
# 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.