Skip to content

Conversation

@Half-Shot
Copy link
Member

Needed so that Element Web and friends can specify they want to use sticky events (to match up with slot permissions behaviour).

Copy link
Member

@BillCarsonFr BillCarsonFr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. But I think we need to make some clean-up on the different options.
We can probably merge multiSfu and preferStickyEvent to a single userMatrix2_0 option

@Half-Shot Half-Shot changed the title Add ability to specify sticky events in URI. Combine preferStickyEvents with useMultiSFU and add a url parameter Oct 28, 2025
label={t("developer_mode.multi_sfu.label")}
description={t("developer_mode.multi_sfu.description")}
checked={multiSfu}
disabled={!stickyEventsSupported}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note, we should have been checking this. MSFU can't be enabled without sticky event support by the homeserver.

@toger5
Copy link
Contributor

toger5 commented Oct 28, 2025

So this implies, that we will disable the state event based multi sfu case?

@toger5
Copy link
Contributor

toger5 commented Oct 28, 2025

In that case we really should rename multi sfu to sth more general like Matrix2.0 mode (use sticky events, multi sfu, and m.rtc.member instead of m.call.member)

@Half-Shot
Copy link
Member Author

Half-Shot commented Oct 28, 2025

So this implies, that we will disable the state event based multi sfu case?

I think we were already only running multisfu on sticky events based on the code, I've just removed the single SFU sticky event use case.

In that case we really should rename multi sfu to sth more general like Matrix2.0 mode (use sticky events, multi sfu, and m.rtc.member instead of m.call.member)

I've been trying to come up with a name, but I don't really know how to describe it to power users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants