bug: support for MSC4143 is not advertised #2216

Closed
opened 2026-09-08 14:37:24 +00:00 by Henry-Hiles · 2 comments
Member

What is the bug?

Continuwuity does not advertise support for MSC4143 in /versions, breaking calling in clients such as Gomuks. Since MatrixRTC is supported, including transports, this should be advertised.

Steps to reproduce

Start a call in up-to-date Gomuks on a Continuwuity server.

Server name and version

continuwuity 26.8.1 (64f5a23)

Additional context

#2183 tried to fix this, but incorrectly only enabled it if sticky events were enabled. It should be enabled if transports are defined at all, probably, or just always.

### What is the bug? Continuwuity does not advertise support for MSC4143 in `/versions`, breaking calling in clients such as Gomuks. Since MatrixRTC is supported, including transports, this should be advertised. ### Steps to reproduce Start a call in up-to-date Gomuks on a Continuwuity server. ### Server name and version continuwuity 26.8.1 (64f5a23) ### Additional context #2183 tried to fix this, but incorrectly only enabled it if sticky events were enabled. It should be enabled if transports are defined at all, probably, or just always.
Member

For those that haven't got around to update, the workaround is simply to advertise "org.matrix.msc4143": true via the reverse proxy.

Example Caddyfile
https://matrix.yourdomain.com {

    # other shenanigans here
    # ...
   
    handle_path /_matrix/client/versions {
        header {
            # these headers match what Continuwuity returns
            Access-Control-Allow-Origin `*`
            Content-Security-Policy `default-src 'none';frame-ancestors 'none';form-action 'none';base-uri 'none';sandbox`
        }

        respond <<JSON
            {
            "versions": [
                "r0.0.1",
                "r0.1.0",
                "r0.2.0",
                "r0.3.0",
                "r0.4.0",
                "r0.5.0",
                "r0.6.0",
                "r0.6.1",
                "v1.1",
                "v1.2",
                "v1.3",
                "v1.4",
                "v1.5",
                "v1.8",
                "v1.11",
                "v1.12",
                "v1.13",
                "v1.14",
                "v1.15",
                "v1.16",
                "v1.17",
                "v1.18"
            ],
            "unstable_features": {
                "computer.gingershaped.msc4466": true,
                "org.matrix.msc4155": true,
                "org.matrix.msc4174": true,
                "org.matrix.msc4354": true,
                "org.matrix.simplified_msc3575": true,
                "uk.half-shot.msc2666.query_mutual_rooms": true,
                "uk.half-shot.msc2666.query_mutual_rooms.stable": true,
                "org.matrix.msc4143": true
            }
            }
            JSON
    }
}
For those that haven't got around to update, the workaround is simply to advertise `"org.matrix.msc4143": true` via the reverse proxy. <details> <summary>Example Caddyfile</summary> ``` https://matrix.yourdomain.com { # other shenanigans here # ... handle_path /_matrix/client/versions { header { # these headers match what Continuwuity returns Access-Control-Allow-Origin `*` Content-Security-Policy `default-src 'none';frame-ancestors 'none';form-action 'none';base-uri 'none';sandbox` } respond <<JSON { "versions": [ "r0.0.1", "r0.1.0", "r0.2.0", "r0.3.0", "r0.4.0", "r0.5.0", "r0.6.0", "r0.6.1", "v1.1", "v1.2", "v1.3", "v1.4", "v1.5", "v1.8", "v1.11", "v1.12", "v1.13", "v1.14", "v1.15", "v1.16", "v1.17", "v1.18" ], "unstable_features": { "computer.gingershaped.msc4466": true, "org.matrix.msc4155": true, "org.matrix.msc4174": true, "org.matrix.msc4354": true, "org.matrix.simplified_msc3575": true, "uk.half-shot.msc2666.query_mutual_rooms": true, "uk.half-shot.msc2666.query_mutual_rooms.stable": true, "org.matrix.msc4143": true } } JSON } } ```
Author
Member

You can also run #2218, which fixes this.

You can also run https://forgejo.ellis.link/continuwuation/continuwuity/pulls/2218, which fixes this.
nex closed this issue 2026-09-08 21:43:48 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity#2216
No description provided.