Description:

Add a health check (/health) endpoint that allows orchestration tools to see if a component is up and running.

Potential solutions

Add

Resolving this issue involves going through the handlers in the modules/ tree alongside the matrix client and server specification to flag methods required to be rate-limited. Currently some are, but many are not.

Example of a method with the flag:

resource::method
method
{
    resource, "GET", handler,
    {
        method.REQUIRES_AUTH |
        method.RATE_LIMITED
    }
};
`

Invalidates a user access token

Invalidates an existing access token, so that it can no longer be used for
authorization. The device associated with the access token is also deleted.
Device keys <#device-keys>_ for the device are deleted alongside the device.

Spec: https://matrix.org/docs/spec/client_server/r0.6.0#post-matrix-client-r0-logout

Some helpful steps:

• add route to routes

The most important feature would be to export room encryption keys per room. This would allow, for instance, an old member of an E2E encrypted room to supply keys to a newer member so they can read history prior to their join.

The function export_keys from the Ru

Sorunome has inline custom emoji things for matrix (there is also somewhere a Spec proposal for this). Basically we need to convert mxc links to real urls in text.

Currently there is the option "Create conference calls with jitsi" which you can enable in settings.
As the jitsi-related stuff got removed this option should not have any meaning.