I like this idea.
Well making “contact Requests” (or better “incoming emails”) more visible, is number one on the list of major things that are blocking the usability:
Not sure how the new “Emails activity” (tab?) is going to look like, but here it is:
1 Like
For the record here, a related problem.
Unfortunately the list of emails is currently not nice to use, because it is not synced with the INBOX on the server. That means every email currently needs to be deleted (or moved) separately on the server and on every deltachat device. https://github.com/deltachat/deltachat-core/issues/195
1 Like
removing them if they are removed from the server doesn’t sounds that good, but also it is true they are a pain to deal with and to remove, they would be not a trouble if something like I said in this comment: No contact request is poping up is done.
Because you want all email to get shown, and your email traffic and usage allows to handle all email in deltachat, you might not have realized it, yet. But not showing every email in deltachat is a crucial default. Just as not bothering the user in deltachat by requiring to manually dismiss and delete each email also in deltachat again.
The good thing of the minimal set of chat listening preferences is, that it should also actually allow to enable the automatic handling of all emails in deltachat (not only known contacts). (For when your email traffic allows it and your usage requires it.)
In addition to syncing changes with the server, this view probably also needs a limit (500?) to only keep the latest emails locally if the INBOX is huge.
I usually want to delete the messages from my inbox because I know I have them in Delta Chat, but it is true that maybe it is better to remove contact requests that were removed with another MUA, so I agree,
I think you had open an issue for that, so please lets keep the topic here around “Make Contact Requests more visible” I need this 
Yeah, your workaround to let the server auto-delete and handle only the deltachat “Emails” works, if I wouldn’t need the emails in the classic MUA.
I need “Emails” (contact requests) more visible too, but not everybody wants it (and thus shouldn’t get disturbed by emails). So I think it wont’t and shouldn’t happen as a default.
Consequently, however, because configuration options shouldn’t happen in a way that prevent or don’t allow proper customization for yet others, I collected the optimized design.
With its 3 easy presets (similar to the limited “show emails?”), but based only on 4 more detailed options (not too much to implement), it should allow for full customization for everybody!
how is a badge with a number disturbing???
I am talking about this request(read initial post) I think it should be this way by default, to let people know they have emails from classic MUA in an unobtrusive way, that is healthy for people that are using DC right now and are complaining about they are missing contact request due to this view is “hard to check”
The icon is not disturbing for me, and I’m sure also not for you. 
But likely for my grandma, she may also inadvertently tap on it and not know what tapping does in the other activity.
There will always be some differences in the personal preferences, thus I don’t think that everybody agreeing on every aspect of a single default would be possible, and it’s thus much more sensible and important to have a set of configuration options that really covers most users.
Preferences also change over time, I for example only changed what I think would be a good “factory” default for the “Email” (contact requests) view. (From show it by default to not show it by default.) This is because of the improvement in (Classic email listening: "start-chat" metrics for classic email client messages (max. length & newlines)) to detect emails that should start a new chat.
With this email-listening in place, I think it could become obsolete for most “default” users to manually check the “Emails” for chat requests or opportunities in deltachat. All one may not even have to know at first then, is, that truly short email messages from known contacts directly open a chat, without much false positives (due to the max. 250 characters with max three newlines condition).
yeah but I am not talking about my preference, this is about an “easy” solution to what every user I know reports to me:
they lost contact request
they and your grandma don’t even know about this “Contact Requests” thing and when I try to explain it, they realize this is a pain to go and check this to check if they have new contact request
But wait, that’s the same reason why I like to completely get rid of having to tell others that they have to keep looking out for new emails (contacts requests) in deltachat.
I think deltachat’s email-listening should do that, with almost no chats opened due to classic emails.
It’s different for myself, I’d like to be able to also check emails in deltachat, so I would enable the “show contact requests”.
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
well i understand @Massick totally. an increasing number always yells out “there is something to do!” … “there is even more to do!” …
1 Like
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
also this will add an extra step to access contact requests, the good thing is that we could keep the QR button