search

element-hq / element-meta

Shared/meta documentation and project artefacts for Element clients
75 stars 12 forks source link

Add a way to temporarily make EVERYTHING notify you #1578

Open turt2live opened 5 years ago

turt2live commented 5 years ago

eg: /noisy 5m or something

aaronraimist commented 5 years ago

and optionally, automatically have everything notify you for a few minutes after you send a message in a channel in case people forget to reply/mention you

aaronraimist commented 5 years ago

vector-im/element-web#7796 is for the opposite of this

sandys commented 5 years ago

this is needed as well as making this enforceable by administrator on a per-channel basis. this is essential for critical chat messages, etc.

Also, this needs to be coupled with email notifications. it cant just be app/web notifications.

lampholder commented 5 years ago

Personally, I can't see when I'd want everything to be noisy (I'm in a lot of rooms) - what use cases are we thinking of? I would however love for 'potential replies' to be noisy by magic.

I'm really not sure about administrators' being able to enforce this - ultimately its up to the client how notifications are handled, so if Riot did implement non-optional notifs I wouldn't expect other clients to honour this. What we could do would be to support 'administrator-recommended settings' that the UX could warn you about when your settings were not aligned?

sandys commented 5 years ago

There are two questions you are asking and I'll attempt to answer them:

  1. What is the use when you can't see it "personally" : you understood it correctly. It is not meant for your usecases but for others. As a further justification, I'll paste the conversation about mandatory alerting and admin control on this from the Hipchat/Stride bug tracker. https://jira.atlassian.com/plugins/servlet/mobile#issue/STRIDE-17

For a lot of us, chatops are mission critical. We are not using this as a convenient chat tool, but as a significantly important email replacement. We have used these for anything from server down to field operations incidents. So mandatory notification for certain channels are critical for us. For others, who don't use chatops in this way - this feature is an annoyance at best. That is a UX question and solvable through great UX choices. You don't need to adopt the behaviour that I need.

  1. Uniformity of clients - two points here : the email notifications that I mentioned previously are indeed a foil to individual behaviour of clients. In fact I would argue you are simplifying this problem, much more than even you realise. For example, Xiaomi android phones have this weird notification control behaviour (with whitelisted apps). So email notifications is an acceptable backup. Secondly, a lot of us are looking to riot as the client we are going to use. For me personally, it's going to be through riot+modular. This question is left to you guys to decide.