Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Keywords to disable notifications #689

Closed
raphj opened this issue May 20, 2022 · 2 comments
Closed

Keywords to disable notifications #689

raphj opened this issue May 20, 2022 · 2 comments
Labels
A-Notifications O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team X-Spec-Changes Z-GetYourUpdates

Comments

@raphj
Copy link

raphj commented May 20, 2022

Your use case

What would you like to do?

I'd like to be able to define keywords or regular expressions that will disable the message notification (possibly for some channel specifically). And maybe a maximum message length (if the message is longer, produce the notification). It would be like the notification keywords that already exist, but opposite.

Why would you like to do it?

I have notification enabled for each message. This is usually fine because the channels I'm in are quite low traffic and I want to be able to passively follow discussions while doing something else. However, there are messages that don't warrant any notifications. There's no way I'd meaningfully react to such messages and those can wait the next time I open Element.

For instance, it is the birthday of somebody and people are used to say "Happy birthday X!" in a specific channel. This is nice and warm, it also does not require being notified. The birthday lasts for the day, the messages can wait a few minutes or hours to be read.

How would you like to achieve it?

I'd like to define a list of keywords or sub-strings like "Happy birthday" that will disable the notification for messages containing it, possibly restricted to a channel. It's not perfect, because I could miss critical information in message like this: "Happy birthday X! By the way, [CRITICAL INFORMATION]" so a regular expression or defining a maximum message length could be useful but then again, the critical information will be seen later and maybe it should belong to a separate message.

Have you considered any alternatives?

I considered temporarily disabling notifications for the channel in which these messages are sent but I still want to be notified for the other messages in this channel.

Additional context

No response

@t3chguy
Copy link
Member

t3chguy commented May 20, 2022

Notifications are handled by both clients & servers, I suggest opening this issue on https://github.com/matrix-org/matrix-spec

@robintown robintown added S-Minor Impairs non-critical functionality or suitable workarounds exist A-Notifications X-Needs-Design X-Needs-Product More input needed from the Product team X-Spec-Changes O-Uncommon Most users are unlikely to come across this or unexpected workflow labels May 20, 2022
@kittykat
Copy link
Contributor

kittykat commented Oct 5, 2022

Hi, I'm going to move this issue to Element meta discussions as we need to consider it cross-platform 👍

@kittykat kittykat transferred this issue from element-hq/element-web Oct 5, 2022
@element-hq element-hq locked and limited conversation to collaborators Oct 5, 2022
@kittykat kittykat converted this issue into discussion #690 Oct 5, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
A-Notifications O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team X-Spec-Changes Z-GetYourUpdates
Projects
None yet
Development

No branches or pull requests

5 participants