File

mod_http_oauth2: Limit revocation to clients own tokens in strict mode RFC 7009 section 2.1 states: > The authorization server first validates the client credentials (in > case of a confidential client) and then verifies whether the token was > issued to the client making the revocation request. If this > validation fails, the request is refused and the client is informed of > the error by the authorization server as described below. The first part was already covered (in strict mode). This adds the later part using the hash of client_id recorded in 0860497152af It still seems weird to me that revoking a leaked token should not be allowed whoever might have discovered it, as that seems the responsible thing to do.

# Introduction

This module adds a room configuration option to hide inline media from
unaffiliated users in MUCs and display them as links instead.

This can be useful in public channels where content posted by users should not
be shown by default.

# Configuring

## Enabling

``` {.lua}
Component "rooms.example.net" "muc"
modules_enabled = {
    "muc_restrict_media";
}
```

## Settings

A default setting can be provided in the config file:

``` {.lua}
muc_room_default_restrict_media = true
```