I’m not against the unread notification itself (I need it myself) but the need of a new icon. It can be handled differently to what @adbenitez ask for.
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
don’t be a dork, did you read:
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"
now stop being a dork
now that you need to always have the last word, I’ll wait here for your next hater comment
I agree to " there are a real necessity for contact requests awareness when email interaction is set to all".
how to show that isn’t that important. a rising number or another simple indicator should be ok.
most important is that it comes!
Is someone working on that issue?
Once true email-to-chat interaction is a supported default based on simple start-chat metrics for email messages and a More useful **chat interaction** setting is there, the hard necessity to show emails to catch contact requests should actually be softened a lot, because chat qualifying emails will then be simply received automatically.
Nevertheless, showing emails is still a very necessary feature to be able to check one’s email inbox, and so much required to be able to reply or answer to a classic email with a quick (interim) chat.
We need this too to see errors in smtp delivery! (one use case).
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
- 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
- or contain the original
Message-IDin the text body
At the end: There is still no indicator which shows a change or new mail in “contact requests”.
That’s the issue.
I think it’s useless to talk about that further. The issue is clear and someone needs to attack it :-/
In the moment I havn’t the knowledge, otherwise I would do it.
Agree, and second.
IMHO the development in the past and the future shows traveling, talk, features, and issues
(+/- amounts and direction), i.e. a progress that could benefit a lot from actually targeting basics and known robust usability issues like this one, and others.
I think that, to contribute to this, we could move the option, (: / contact requests) to a bubble with the name “emails” at the end of the chat list. With your new message counter included.
except that the end of the chat list is too far down. I have 3 pages of chats (mostly with someone who does not use DC but a classic MUA) and it might get more. I will never realize it if there is an extra entry at the bottom.
PS: Maybe I just misunderstood you; what do you mean with “a bubble at the end of the chat list”?
Yes, it was that, you understood well, and you’re right.
yeah, at the end isn’t good, if devs would like to use a chat-like solution as you suggest (an entry in the chat list) it should be shown at the top something like this is what Spike does
I had tons of chats, it is REALLY annoying to scroll to the bottom and the chats list scroll doesn’t provide a way to scroll faster
Lots of things can be done here.
No way to scroll down faster? Put some arrows there (or let the user choose if he/she wants it)
An entry at the top can be annoying, remember they are contact requests, although if we implement some starred sorting or something like that, this contact-request-chat won’t be at the top.
What are you discussing?
The idea that @adbenitez posted and re-using the chat list view for the emails, and an option to hide the button for those that don’t want it, is pretty good IMHO.
this is solved in versions 0.9xx, now if you have email interactions set to all, contacts request from classic email are handled the same way than contact request from DC clients