-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Replying to a message containing a ping causes the intended recipient(s) of the ping to be pinged again #7874
Labels
Comments
This'll automatically be fixed once the fallback is removed from the replies |
Is there any reason why homeservers don't first strip the fallback before checking for push rules? |
That's up to the homeserver, not Element, would recommend you take your question to whatever homeserver you are wishing did that (really though it would have to be specced as such because clients apply push rules too) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This happens for both room pings and user pings. Examples:
(As seen by users other than Ruff_Wizard. User Ruff_Wizard does not get themself pinged by their reply, but the rest of the room does.)
(As seen by user Ruff_Wizard. User Ruff_Wizard gets pinged by a message replying to one containing their name.)
It shouldn't work like this; this system assumes that someone necessarily wants/needs to get pinged just because another person is replying to a message which contains their name/a room ping. If someone wants to ping the person or the room again, they can simply insert another ping in the text of their reply. The system shouldn't ping every time the intial ping is replied to.
The text was updated successfully, but these errors were encountered: