MSC4515: RTC Transports discovery for widgets - #4515
Open
BillCarsonFr wants to merge 3 commits into
Open
Conversation
BillCarsonFr
force-pushed
the
valere/rtc/widget_action_rtc_transport
branch
from
July 22, 2026 14:23
8c7771b to
ee29ea2
Compare
BillCarsonFr
force-pushed
the
valere/rtc/widget_action_rtc_transport
branch
from
July 22, 2026 14:40
ee29ea2 to
8df2e5a
Compare
BillCarsonFr
marked this pull request as ready for review
July 22, 2026 14:42
turt2live
changed the title
turt2live
reviewed
Jul 22, 2026
Member
There was a problem hiding this comment.
Implementation requirements:
- Widget (using)
- Client (supporting)
Member
There was a problem hiding this comment.
Client implementation: gomuks/gomuks#737 (with matrix-org/matrix-widget-api#165)
turt2live
added
proposal
This was referenced Jul 22, 2026
5 tasks
robintown
approved these changes
Jul 27, 2026
robintown
left a comment
robintown
left a comment
Member
There was a problem hiding this comment.
As soon as the LiveKit authorization endpoints become authenticated CS API endpoints, I suppose this one action will no longer be enough to implement an Element Call widget. But this is a sensible action to have in general.
Comment on lines
+118
to
+121
| ## Dependencies | ||
|
|
||
| This MSC builds on [MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143) (which at the | ||
| time of writing have not yet been accepted into the spec). |
Member
There was a problem hiding this comment.
Also widgets are generally not in the spec
Co-authored-by: Robin <robin@robin.town>
Co-authored-by: Robin <robin@robin.town>
turt2live
reviewed
Jul 28, 2026
| @@ -0,0 +1,121 @@ | |||
| # MSC4515: RTC Transports discovery for widgets | |||
Member
This was referenced Jul 30, 2026
stefanceriu
pushed a commit
to matrix-org/matrix-rust-sdk
that referenced
this pull request
Aug 7, 2026
Mostly plumbing to get the new WidgetAction [RtcTransportsAction](https://github.com/matrix-org/matrix-widget-api/blob/master/src/interfaces/RtcTransportsAction.ts) to call the new client API `Client::rtc_transports` introduced in #6789 **And** a change on the ffi bindings to make the `is_livekit_rtc_supported` to use this new rtc discover API. There is a boolean added to decide if it can fallback to the old well-known, it is set with a default value, so it is not technically a source breaking change, we want to enforce the new way of getting transport but we leave an option to steal fallback to well-known Implements [MSC4515](matrix-org/matrix-spec-proposals#4515)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rendered
Implementations: