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

How about a message type which will never trigger notifications? #2031

Open
rowskilled14 opened this issue Dec 14, 2024 · 0 comments
Open

How about a message type which will never trigger notifications? #2031

rowskilled14 opened this issue Dec 14, 2024 · 0 comments
Labels
improvement An idea/future MSC for the spec

Comments

@rowskilled14
Copy link

rowskilled14 commented Dec 14, 2024

Suggestion
Something like /silent followed by a message, being the client usage. It of course will need a Matrix spec to support the functionality before clients can implement that type of format.

The idea being, /silent test message 123 would never trigger a notification for the other user, pending their specific settings. Keyword notifications or perhaps a special setting on their end could force override this rule.


The use case for this could extend to many scenarios, but would typically revolve around the idea of: "I have something I want to tell the other user, but it isn't important right now and I have a particular reason to not bother them at this very moment, yet I still want to send the message right now." It could be that you know someone is in a meeting, someone is at an appointment, or it's very late at night and they're probably asleep. In each case, you might want the message to be ready and waiting for the user as soon as they're free, but you don't want to be a nuisance in the meantime.

Some bot/scripting/automated/API functionality could be utilized from this as well for similar lines of reasoning.

The message would show up with slightly different formatting in clients to indicate that it was a silent message. Something resembling a whisper type message from other chat systems. Nothing massively distracting, but just a small indicator of sorts.

Users could specify in their client a specific setting for how to receive these messages as touched on above. These settings could include:

  • The ability to fully disable this feature on a per-room basis, a per-user basis, and globally
  • The ability to choose between:
    • silent notifications still visually appear, but are silent/not noisy
    • OR
    • silent notifications not appearing at all until the user manually checks the client
  • The ability to listen for keywords to override this feature

I'd be happy to submit an MSC if I could receive some guidance on how to approach this. I'm sure I'm overlooking a lot of definitions and potential issues, and I'm open to real feedback and discussion.

Thank you very much!

@rowskilled14 rowskilled14 added the improvement An idea/future MSC for the spec label Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement An idea/future MSC for the spec
Projects
None yet
Development

No branches or pull requests

1 participant