When sending a message, if I click and drag the send button, similar to the action when you lock the recording of an audio message, mark the message as important. Just clicking the send button sends the message as a regular one. The receiver can set two types of message notification and be able to only get notifications of the important ones
There’s just one kind of message and notification
Not sure about the best interface, but I agree that such a feature would be useful. Here are the related email standards to make it easier to search - RFC 4021, RFC 2156, low & high priority, normal & urgent header:
The way of doing it seemed pretty intuitive how I described it, but can be other nice ways to do it
Like doing some action to the last message like slide or double tapping it…
I was thinking that this would be a kind of that msn messenger thing… the nudge?? But well done
TBH I don’t like the word “important” in the context of an instant messenger. Sounds too corporate.
Also I’m not really getting how the feature is actually going to be used. If you’re chatting with a person who has set up notifications this way, do you keep sending normal messages to them knowing that they won’t get notified, and only send an “important” one when you want them to reply?
Telegram has what seems like the opposite: a “Send without Sound” button, which appears when you long-tap or right-click the send button.
For the really important stuff one can just start call.
We can name it different, the name it’s not important to me, maybe:
we can brainstorm about the name, sure can be one more precise.
The use case is this: I want to be able to diferentiate between messages that wants and answer sooner than later and messages than it’s just something that can be answered at anytime.
You are right, important stuff should be a call. Maybe this could be something in between the message and the call.
Didn’t know that telegram already does it! Then it’s not that weird what i wish… but they do it “noisy” by default i want it “silent” by default 
Delta Chat prefers using established standards where they exist. Instead of coming up with custom terminology, I would just use the email headers and names already introduced in the above RFC:
Especially that there’s actually a difference in meaning between important and urgent. It’s already unsettling how some webmail clients confounds the two!
thanks for explaining it that clear! In the first message you already linked the standards but didn’t pay enough attention… When I see something too technical… My thinking is that I can’t understand it and I avoid it.
I can’t change the subject, but If someone could do it, will be more appropiate to something like: “Send urgent, normal and non-urgent messages”
I totally get your idea but I think forcing all users to send “silent” messages by default is not what they use a messenger for.
I personally know the feature from Telegram (Send without sound) but as a long-term TG user I used it once or twice in my whole lifetime.
Maybe it makes sense to implement the “urgent” header from above RFC and provide some kind of special notification which tells the other person that this message is really important and needs some quick reply.
So the three priorities would make sense like this for me:
urgent: Special notification on the other end with an exclamation mark or a special notification sound
normal: All other messages
non-urgent: Same functionality like in Telegram with the "Send without Sound, so there would be no notification and no sound after receiving the message
But I also think these messages should be marked with the priority too in the UI, so that users can see whether a message was urgent, normal or non-urgent.
What comes to my mind would be an exclamation mark near “urgent” messages (
), a striked through speaker (
) or a down-arrow like most email programs use for these mails (
) for “non-urgent” messages and no sign for “normal” messages.
Also note that it’s also a sensible option to combine the three levels into two (e.g., only differentiate between urgent and everything else).
A new filter could be introduced on the interface that would allow you to first go through only urgent messages after you opened Delta Chat and only then proceed to read all other chats and messages. Withing a given chat, we may even consider urgent messages as if they were “pinned” and provide a filter to show only these or interpret them as bookmarks to jump to. Of course, the recipient would also be able to override and make any of them non-urgent (i.e., unpin them).