element-hq / element-hq/element-android
“Impersonal” pane for automated and unhasty messages
- Lingua principale
- Kotlin
- Stelle
- 3.7k
- Fork
- 917
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I really love that subdivision of rooms into inbox, direct chat and chat rooms! However, there is a further category which might deserve its own category: Impersonal messages. With this type of message, I mean either automated or E-Mail-like messages, which are usually not stemming from a human, but are more like status updates or pretty unimportant/unhasty stuff.
For example when you have a bot surveilling your server, which is sending you some system notifications about an available update etc. Another example would be more future-thinking, like when E-Mail bridges get to be a thing or services even directly use Matrix. So for example parcel status – here I usually get up to five E-Mails per shipped parcel, notifying me about each step.
It would be cool if those types of messages would not be sorted among my direct chats or chat rooms with my friends and therefore get another category on their own. Furthermore, these messages usually are not that important. I for example check my instant messages quite often each day, but I check my E-Mails only once or twice a day, because I don’t want to be annoyed throughout the day, when I have better things to do.
So my preferred solution would be a fourth category in which both direct chats and chat rooms of those types could be sorted in. Additionally, it would be good if we could specify for each of those conversations, if new messages appear in the inbox pane, or not (for not littering my inbox). If messages can have priorities like E-Mails, it would also make sense for them to only appear in the inbox if they have a priority above standard level – then I won’t notifications of my bot about pending updates, but I could immediately recognize a server crash, intrusion detection or whatever… 😉️
What do you think about this in general?
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.