11 Feb
2019
11 Feb
'19
11:25 p.m.
On 02/07/2019 10:54 AM, holger krekel wrote:
Hey Marco,
On Wed, Feb 06, 2019 at 01:56 +0100, Marco Vittorini Orgeas wrote:
? This contradicts what happens with the "overtaking of ownership bug"
(see my quote of you on my previous email).
Under which condition then DC move messages away from the INBOX?
On 02/03/2019 10:43 AM, holger krekel wrote:
Others have
different expecatations: Alice expects a webmail-written top-level
mail to arrive with Bob's webmail-interface ... the fact that Bob has with DC
previously chatted with Alice does not change that expectation. On Sun, Feb 03, 2019 at 03:47 +0100, Marco
Vittorini Orgeas wrote:
So any mail from a
contact already in the INBOX remains in the INBOX when
using Delta? This would litter the INBOX with a myriad of "small" delta chat
messages, avoiding which is the whole purpose of the shared scenario. [...] let's say user@domain1 is happily
exchanging
mails with user@domain2, then user@domain1 starts to use delta to reply to
user@domain2, over-taking ownership of future communications with
user@domain2.
What happens if user@domain1 want to continue using its MUAs to communicate
with user@domain2 ?
If user@domain1 mails with a non-DC MUA then those messages
remain
in the INBOX [*] -- so accessible to user@domain1's MUA. They are also
shown in DC as a chat -- is that what you take issue with?
There is no "sole purpose" to the account sharing than trying to balance
and adapt with what we perceive as user expectations. We've had many
discussions with people on and off line -- if there would be one easy
obvious solution we'd maybe go for it ;)
And I, for one, would like to hear and discuss with these people...where
are they?
The only community contact we had on the topic was back on this list,
and quite some persons were engaged in the discussion, but at the end we
had a "roger" from your side with the intent of suspend the decision
after the last October meeting...and after silence now we have a new
major release focused on UI polishing. The community process over
engagement and discussion is pretty opaque!
As for user expectations: those are always various in content and
quality, and often times are confused: reading the DC "brochure" on the
site, one understands that DC gives a chat experience over the email
infrastructure without getting in the way.
Many had the impression that DC is instead evolving as a fancy MUA,
which gets in the way, but I got the impression that their opinion seem
not to weight much.
Correct me if I am wrong on this.
Here is the thing: we can not and do not try to satisfy "everybody"
which if you think about it is an awfully abstract abstraction.
Rather we try to find and balance the code and UI to meet what we
perceive as user expectations that seem interesting and relevant to us ...
It would be interesting to get some definition of "us" for the rest of
us ;) .
For example, some users would be interested in integrating DeltaChat with
Google Drive ... and our attitude is somewhat complex to that ...
after all, people use the centralized, tracked and cleartext gdrive system
to get someting done ... something that appears to them maybe more important
than being hidden from the Google sysadmins and whoever they work with.
We are reluctant to do much special work or prioritize around integrating
with GDrive systems, however. If folks join who want to develop on this
the situation may change ;)
Holger, I am not discussing adding "space jet" features nobody would
use: I am instead quite concerned with the direction and reliability of
the project if it wasn't clear.
The beautiful thing about DeltaChat is also this: we
have MPL-licensed
the DeltaChat core library and it's quite easy to write UIs on top of it.
Just don't name it DeltaChat but otherwise there is nobody stopping
you from working with others even within commercial settings. If
you want to change things in core talk with us and we'll see what
we can do.
I think you're mistakenly assuming I am somewhat interested in
developing and commercialize/re-package some DC related software, who
I'm definitively not.
Also, I don't think that suggesting a fork in the face of constructive
criticism is the best thing for DC, but thanks for have reminded me I'm
free to do so.
--
Marco