-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Stabilize support for MSC3952: intentional mentions #25267
Comments
Also see matrix-org/synapse#15487 for stabilizing this in Synapse. |
Note that this will be in the v1.7 release of the Matrix spec (if that needs to be checked). |
Changes are drafted, will open for review following synapse changes and/or the EW user testing sessions. |
@kerryarchibald I had a thought: should we update the buttons in the notification settings to disable the new push rules (in addition to the old)? Eg if you disable mentions it should probably toggle both versions? Maybe this would be done with the settings UI rework though. |
@clokep good thought! We should have that in place for the testing session. I'll make a ticket and coordinate with Janne |
Looks like the Synapse PR was merged. Is this ready to progress now? |
It should be fine to, I think the element web code won't be used unless v1.7 is enabled in the server anyway? Not 100% sure how it is implemented. |
@kerryarchibald Shall we close this or is it pending #25434? |
Your use case
MSC3952 has been accepted, we should stabilize support for it by using the stable identifiers:
org.matrix.msc3952.mentions
->m.mentions
.org.matrix.msc3952.is_user_mention
->.m.rule.is_user_mention
.org.matrix.msc3952.is_room_mention
->.m.rule.is_room_mention
And we should de-labs it after testing.
Have you considered any alternatives?
N/A
Additional context
See #25266 for a known bug in the implementation.
The text was updated successfully, but these errors were encountered: