It can be very annoying. I personally can’t bear any unread notification, so this badge and number combination would disturb me. On the other hand, I don’t wanna miss any important mail. The answer could be something more subtle, maybe a red dot next to the menu button? (a tiny little one)
it is not a notification, it is just a silent badge in an icon, also it is more useful to have a number than a dot, because if you have contact requests and receive a new one you will not know it, so you will miss it again
I disagree, that is only if you are in the chat list and have nothing more interesting to do, but in a chat you don’t even see this badge,
also it could be “9+” if the number is going too big, it don’t need to be “1000”
my main interest in using a number is to be aware of new contacts requests, using two-state signal like that red dot, will be a bit useless and users could still lost contact requests, I think the “9+” thingie could be a good point in the middle, not too stressful and still a bit more useful than a dot
Exactly, the badge is for people that want to be “annoyed” with a badge that has an “annoying” number inside, that actually want to know that “there is something to do!”
by default DC doesn’t show classic email, so there are no such problem, the icon can even be hidden, and if user has email interaction set to all it is because he/she actually want to be aware of emails, so we are talking about a fictional issue of chronic number phobia that don’t even exists, badges with numbers are much more useful than a dot, are used a lot and if you consider this stressful then remove them from the Delta Chat launcher icon because people could have a panic attack
but before we start a pointless discussion between a boring dot and a sexy number
I have to say that there are a real necessity for contact requests awareness when email interaction is set to all, so I don’t want to waste more time in this, whatever improve the current situation, I am ok with it
no pointless discussion (in that case, what’s the point of this forum?), you still stuck in that badge idea. @adbenitez only because all the hours you spent on gimp we don’t have to fall in love of your paintings, more so, dot are sexier than numbers, ask anyone
what I meant with “pointless discussion” is that both solutions are “good enough” and that we just need a way to be aware of contact requests not keeping endlessly in theory.
the only one that seems stuck is you, I already say that I am ok with your dot or with whatever will make contacts request more visible, but instead you keep trying to go for a real pointless discussion,
about gimp, it was not that hard to do, and that was just something to start with, I don’t really care if it is a badge, a dot or a friendly pink pony popping up on the screen, just something that "Make Contact Requests more visible"
I think we need email displaying for various reasons. Just not for manually looking for “contact requests” or email delivery failures.
The failures need to be detected automatically, and may only need to be displayed to the user in a special error message with the raw text, if they can not be parsed and assigned to a recently sent message that does not yet have a delivery receipt.
Most if not all? failure receipts
come From: MAILER-DAEMON@
And the text body contains at least this header data from the original message:
Which should already be sufficient to detect the affected, recently sent message.
But some failure receipts even contain
an X-Failed-Recipients: header.
or contain the original Message-ID in the text body