-
Notifications
You must be signed in to change notification settings - Fork 384
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
user name mention notifications happen when user name is mentioned without any qualifying prefix/suffix #3011
Comments
FYI, in Element, you can turn off notifications for "Messages containing my display name" and "Messages containing my username". This will stop notifications when someone just writes "be", but will still notify you when someone writes your full Matrix ID. It isn't quite what you're asking for (you won't get notified when someone writes |
@uhoreg I have tested this. Like you explained switchting it off disables all notifications including the "@" ones. This isn't an option for me because then I am missing "@" mentions. In many highly acitve rooms I have disabled notifications except "mentions & keywords". |
I think being notified when a message contains "be" is expected behaviour if your username is "be" and you have "messages containing my username" enabled. The fact that you then aren't pinged by @mentions is covered by matrix-org/matrix-spec#353. Certainly this stuff is a total mess, and it pains me that we've not had the time to rework it. |
Describe the bug
My Matrix user name is simply
be
, which is a common English word. Element triggers a notification anyone uses my user name, which is almost always not actually trying to send a message to me. This makes notifications from Matrix clients basically unusable. User name mentions should only trigger a notification with an appropriate prefix such as@
or a suffix such as:
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should only be notified by messages specifically directed at me.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
I reported this first on the Element Web tracker and they directed me here.
The text was updated successfully, but these errors were encountered: