Skip to content

Conversation

jaywink
Copy link
Member

@jaywink jaywink commented Jan 21, 2021

If Synapse has the related admin api (matrix-org/synapse#9168), fetch power levels and add them to the result of the verify user in room.

The response structure is the m.room.power_levels state event content with the users stripped out. The user level is found separately on the higher level to avoid confusion related to all the power levels for users in the room.

If Synapse has the related admin api (matrix-org/synapse#9168), fetch power levels and add them to the result of the verify user in room.

The response structure is the m.room.power_levels state event content with the users stripped out. The user level is found separately on the higher level to avoid confusion related to all the power levels for users in the room.
jaywink added a commit to matrix-org/prosody-mod-auth-matrix-user-verification that referenced this pull request Jan 21, 2021
When the user joins the conference, we catch the
`muc-occupant-joined` event and make them an owner
if they were marked as one during auth.

During auth, if we get power levels back from UVS
(see matrix-org/matrix-user-verification-service#7), we compare the users power level in the
room to "state_default" of the room and if the
user is equal or more, we mark them as owner.
This allows them to do moderation in the Jitsi
conference side.
@jaywink jaywink merged commit ee662c7 into master Jan 22, 2021
@jaywink jaywink deleted the jaywink/power-in-room branch January 22, 2021 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants