Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSC2772: Notifications for Jitsi Calls #2772

Open
wants to merge 2 commits into
base: old_master
Choose a base branch
from
Open

MSC2772: Notifications for Jitsi Calls #2772

wants to merge 2 commits into from

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Sep 11, 2020

Introduces a default push rule to trigger a notification when a Jitsi widget is added to a room.

Impl: matrix-org/synapse#8286

Rendered

This proposal adds the following predefined rules to the default underride rules:
```
{
"rule_id": ".im.vector.jitsi",
Copy link
Member

Choose a reason for hiding this comment

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

we shouldn't ever specify non-matrix namespaces

@turt2live turt2live added kind:core MSC which is critical to the protocol's success proposal A matrix spec change proposal labels Sep 11, 2020
@dbkr dbkr marked this pull request as ready for review September 11, 2020 14:52
and use the existing ones as the unstable versions
@t3chguy
Copy link
Member

t3chguy commented Oct 30, 2020

Hmm, this seems a weird direction given that push rules are on their way out: #2785

@@ -0,0 +1,131 @@
# MSC2772: Notifications for Jitsi Calls

Matrix supports conference calls in rooms througth the use of Jitsi widgets. A user receives
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Matrix supports conference calls in rooms througth the use of Jitsi widgets. A user receives
Matrix supports conference calls in rooms through the use of Jitsi widgets. A user receives


Matrix supports conference calls in rooms througth the use of Jitsi widgets. A user receives
notifications when they receive a 1:1 VoIP call, but currently there are no notifications for
any widget being added to a room, including Jitsi widgets, so user are not notified when a
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
any widget being added to a room, including Jitsi widgets, so user are not notified when a
any widget being added to a room, including Jitsi widgets, so users are not notified when a

Comment on lines +102 to +103
vs `m.jitsi` and `im.vector.modular.widgets` vs `m.widget`. Clients should provide present all three
of these rules as single rule to the user and apply the same mdifications to each one of these rule
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
vs `m.jitsi` and `im.vector.modular.widgets` vs `m.widget`. Clients should provide present all three
of these rules as single rule to the user and apply the same mdifications to each one of these rule
vs `m.jitsi` and `im.vector.modular.widgets` vs `m.widget`. Clients should present all three of these
rules as a single rule to the user and apply the same modifications to each one of these rule

## Security considerations

Implementors must ensure to implement the condition checking for a state event, else there would be
potential for this to be triggered by user without permission to send state events.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
potential for this to be triggered by user without permission to send state events.
potential for this to be triggered by users without permission to send state events.

@anoadragon453
Copy link
Member

The implementation of this MSC in Synapse has been merged: matrix-org/synapse#8286

@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants