-
Notifications
You must be signed in to change notification settings - Fork 382
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
MSC2153: Add a default push rule to ignore m.reaction events #2153
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very plausible.
Co-Authored-By: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
This adds a default push rule to ignore reactions as proposed in [MSC2153](matrix-org/matrix-spec-proposals#2153). By adding it here in the client directly, we can try out the idea early even if it hasn't appeared in the user's HS yet. Part of element-hq/element-web#10208
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
soliciting review from @dbkr as the push rule expert would also be ideal.
Seems like people are generally happy with this one, so: @mscbot fcp merge |
This FCP proposal has been cancelled by #2153 (comment). Team member @mscbot has proposed to merge this. The next step is review by the rest of the tagged people: Concerns:
Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for information about what commands tagged team members can give me. |
This adds a default push rule following the proposal in [MSC2153](matrix-org/matrix-spec-proposals#2153). See also element-hq/element-web#10208 See also matrix-org/matrix-js-sdk#976
This adds a default push rule following the proposal in [MSC2153](matrix-org/matrix-spec-proposals#2153). See also element-hq/element-web#10208 See also matrix-org/matrix-js-sdk#976
I wonder if it makes sense to just merge this as a section in MSC1849. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small thing.
} | ||
``` | ||
|
||
## Tradeoffs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Tradeoffs | |
## Alternatives |
as a general note, I see that, as with the rest of reactions, this is already implemented and we have servers and clients relying on it. |
Team member @mscbot has proposed to close this. The next step is review by the rest of the tagged people: Concerns:
Once at least 75% of reviewers approve (and there are no outstanding concerns), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for information about what commands tagged team members can give me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll also link to the implementations in the PR description to clear the label.
"Requested changes" to note that there's things which need to be done before merge, but not before FCP.
} | ||
], | ||
"actions": [ | ||
"dont_notify" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2624 is now matrix-org/matrix-spec#643
though, we should land/FCP reactions themselves first, which is why we originally cancelled FCP. For now let's just block it: @mscbot concern Reactions don't exist |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to close, as per the review above, is now complete. |
Reactions are considered "metadata" that annotates an existing event and thus they should not by default trigger notifications. This adds a new default override rule that ignores reaction events for the purpose of notifications.
Rendered
FCP Checkboxes
Implementations: