matrix-org

For reasons, signedjson generates instances of pynacl's SigningKey and VerifyKey and then monkey patches new alg and version attributes onto them.

We (Synapse) never use pynacl directly as far as I can see. There are a number of type hint instances which refer to nacl.* when they should instead refer to signedjson.types.*.

I think we should

• replace any uses (including type hints

Background information

• Dendrite version or git SHA: 002c3e0a5ff18c0b36c4c8e6cebea61547c9ac51
• Monolith or Polylith?: Monolith
• SQLite3 or Postgres?: Postgres
• Running in Docker?: no
• go version: 1.17.5

We're currently using lazy_static in some test code. Since it's a macro, it looks and feels a little magic. There has been a less magic alternative for a while in the form of the once_cell crate (whose interface is also available in std in nightly). We should switch to it for better readability.

Wondering if it's possible to add a configuration option for a proxy (or even multiple proxies), specifically SOCKS5, but I would assume that adding support for others might not be a problem if they're prefixed correctly in the config

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

last docker image was updated 5 months ago, but i see more recent commits. I'm having issues with a new install, but i want to make sure i'm on the most recent code before i start asking questions.

https://github.com/gary-kim/riotchat/blob/ff6d4fed087840fade3ed4b394638843c302d0db/src/components/AdminSettings.vue#L46-L55

The label does not properly point to the input because the id of the input is incorrect. This should be a simple one line fix.

Of all the things, I know this is probably... okay, nonexistent on the priority queue, but.

When an invalid / non-existent room ID is given to the -r option, the tool crashes:

# ./synapse_compress_state -p ... -r '!this_is:not.valid'
Fetching state from DB for room '!this_is:not.valid'...
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/database.rs:162: