hey, last week Bjoern visited for a couple of days and among other stuff we discussed "shared" versus "dedicated" accounts. Shared accounts are ones which are used by both traditional e-mail apps (Thunderbird, Webmail, Outlook etc.) and DeltaChat. Whereas dedicated accounts are ones only used by DeltaChat. There has been a lot of negative feedback related to "shared accounts" ... just the freshest one from today's IRC from a new user dropping in: if I send a chat to Joe, he answers, he is on my contact list. Then he sends me a normal email, it will show up in Delta chat, which I don't expect to, unless it is a reply to the chat. This is "expected" from the implementation side: if you accept a contact (opening a chat with a contact implicitely accepts the contact) then all messages, including new "threads", from/to that contact are "owned" by deltachat. Then, the logic / implementation which moves messages from the INBOX to the DeltaChat folder has issues, which lead to messages remaining in INBOX which should be in DeltaChat. the current 0.20 Android version is known to have issues with it but they haven't been found yet. So we have both user expectation mismatch and implementation complexity issues here. The Move-to-DeltaChat actions also cause extra network requests, on a side note. Therefore we think it's better to move towards recommending **dedicated e-mail accounts for DeltaChat**. You may still use it "shared" but there will be no features or much development effort sunk into it. One problem with dedicated accounts is that people can't easily use their address-book to get into contact with each other. There is a potentially nice mitigation for this. Let's presume that when you setup DeltaChat with your dedicated account you may specify your traditional e-mail address so that DeltaChat knows about this address. Then ... - if you receive a mail on the traditional e-mail address (with any MUA/webmail) you can forward it to your DeltaChat account which will automatically open a chat with the original poster. You will see the original poster's message and can type a chat-reply. The original poster will see messages coming from the dedicated chat address. If the poster now also fowards the chat-mail to her delta-address (if it wasn't already a delta-address!), the two delta's would be talking with each other through the dedicated addresses only. - People with dedicated accounts wouldn't get "surprising" e-mail as contact requests. Also there is less chance of dropping back to unencrypted communications because we saw some non-autocrypt mails from a webmailer/thunderbird etc. - DeltaChat could mark contacts/email-addresses if it saw >99% DeltaChat messages with it (maybe a small "delta" or so), allowing to make a choice if you want to contact someone via the delta or their "normal" e-mail address. - DeltaChat can make it easy to share things with the "tied" normal email address to send attachments/pictures etc. DeltaChat would then stop to do the move INBOX -> DeltaChat folder thingie. You could still access your DeltaChat account with thunderbird/gmail-web interface etc. but you'd see the DeltaChat messages in your inbox. Gmail for example would condense 30 replies into a single line so maybe that's not so bad. Note that the question of dedicated versus shared accounts does NOT have any effect on DC's ability to contact other e-mail addresses with arbitrary non-Delta MUAs -- that's fully continuing to work and be supported. so much for now ... feedback welcome. holger _______________________________________________ delta-chat mailing list -- delta(a)codespeak.net To unsubscribe send an email to delta-leave(a)codespeak.net