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

Notication keywords trigger on homeserver domain in MXID #23469

Closed
BurnyBoi opened this issue Oct 12, 2022 · 3 comments
Closed

Notication keywords trigger on homeserver domain in MXID #23469

BurnyBoi opened this issue Oct 12, 2022 · 3 comments

Comments

@BurnyBoi
Copy link

BurnyBoi commented Oct 12, 2022

Steps to reproduce

  1. Add a notification keyword that is a word in the domain section of anybody's MXID
  2. Have someone reply to anyone other than you with that domain in their MXID

(Example: Add matrix as a notification keyword, then have anyone reply to a matrix.org user)

Outcome

What did you expect?

User should NOT get a notification, because the body of the original message and the reply do not contain matrix (in the example given)

What happened instead?

I receive a notification because the user being replied to has matrix in the domain of their MXID, triggering the keyword.

Element "Mentions & Keywords" notification settings set to Noisy with "matrix" keyword set

Message being replied to (Example 1):

Example 2 (with reply that causes a notification):

"@emperorart:matrix.org" MXID shown off

(Note: Neither of these are my account. The notification is only because the one being replied to is on matrix.org)

Operating system

Arch Linux

Browser information

Firefox 105

URL for webapp

develop.element.io

Application version

Element version: 2ef6abb-react-8b54be6f4863-js-cc025ea45844 Olm version: 3.2.12

Homeserver

matrix.org

Will you send logs?

No

@MadLittleMods
Copy link
Contributor

MadLittleMods commented Oct 12, 2022

In the second example with the reply, it makes more sense why it would ping you since the reply syntax has the MXID in it with matrix.org.

event.content.body

> <@madlittlemods:matrix.org> foo\n\nbar

event.content.formatted_body

<mx-reply>
	<blockquote>
		<a href="https://matrix.to/#/!xxx:matrix.org/$123?via=matrix.org">In reply to</a>
		<a href="https://matrix.to/#/@madlittlemods:matrix.org">@madlittlemods:matrix.org</a>
		<br>foo
	</blockquote>
</mx-reply>

bar


For the first example, I'm not able to reproduce with from a normal message that has no matrix string in the body. Can you share the source for that message? Are you absolutely sure that you got a notification sound for it? Can you reproduce with another plain message?

@MadLittleMods MadLittleMods added the X-Needs-Info This issue is blocked awaiting information from the reporter label Oct 12, 2022
@BurnyBoi
Copy link
Author

BurnyBoi commented Oct 12, 2022

For the first example, I'm not able to reproduce with from a normal message that has no matrix string in the body. Can you share the source for that message? Are you absolutely sure that you got a notification sound for it? Can you reproduce with another plain message?

@MadLittleMods The first message is not causing a notification. It just has the green on the left because I clicked the reply to get to it. I just screenshot that one so I could prove the entire message does not contain "matrix" in it. This bug is only about the reply causing a notification.

While the formatted body may technically contain the MXID in the event body and does explain why the bug happens, it's not being presented that way to the user, and neither message actually contains "matrix" from the user's perspective.

@MadLittleMods MadLittleMods removed the X-Needs-Info This issue is blocked awaiting information from the reporter label Oct 12, 2022
@MadLittleMods
Copy link
Contributor

MadLittleMods commented Oct 12, 2022

Thanks for the clarification @BurnyBoi!

Looks like a duplicate of element-hq/element-meta#743, #16863, element-hq/element-meta#744

@MadLittleMods MadLittleMods closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants