7 Jan
2020
7 Jan
'20
9:29 a.m.
Hi drebs, compl4xx :)
while skimming your conversation a quick remark ...
On Mon, Jan 06, 2020 at 03:04 +0100, compl4xx wrote:
it can only be estimated -- F-Droid and apk downloads are not counted at all
and eg in Cuba and elsewhere there are separate app stores that can not
be accessed from the outside.
sidenote: i'd be careful with using "Delta Chat" to designate an actor that
can do or receive things -- there is the "app" and there are
"developers",
maybe merlinux as an organization, but "Delta Chat" per se does not exist :)
"optional" sounds more like what Telegram does. DC does default to E2E,
also for group messages. With verified groups you get guaranteed E2E
also for groups so i guess it's ok to just say "yes" here.
read receipts are "yes" by default. You can switch it off.
probably that's a "no" if deleting means deleting on the receiving side.
It's fine to focus on DC to DC usage here i think. So we can and will
implement self-destruct messages althought he construction is likely
to be "one-sided ephemeral messages" because we want to support
asymmetric organization scenarios, i.e. one DC (desktop) user might organize
a group and retain messages, while people in the field will switch on deletion on
their phones.
definitely "yes" ... postfix/dovecot/exim/... in many cases open source
services
are used even from commercial providers.
cheers
holger
- Is there
a count of "monthly active users"?
No. There is no way to measure this.
Hm, we could ask the NSA?^^ I'd
just leave out the number, many other messengers don't have it either. - How to
succintly express that no specific registration is
required, but that an e-mail account is needed, in the column
"Registration requirement"? Or just say "no" or leave blank?
Let's just say "Email". No need to make it complicated; and it does
require an Email address to work, even if it's not transmitted to Delta
Chat. - I guess
the license can be pulled from github, but if there are
any gotchas it might be good to know.
It's GPLv3+ for Desktop &
Android - but iOS might be another issue.
There is no license on GitHub, probably because GPLv3 is incompatible
with the Apple Appstore. Not sure what license is planned for the iOS
app; for now let's just say GPLv3+.
- Support for which operating systems should
be listed as "Yes"?
Windows, MacOS, Linux, Android, iOS. There is no web
client.
- How to express that there is E2EE only
after the first message?
How does that work exactly for group messages?
"Optional" fits
best for both 2-user and group chats, I think. Or maybe
"Opportunistic", if we can just fill in what we want? - Are
there any limitations for "file transfer" support or should
that just be signaled as "yes"? Same question for voice
recording. (i guess the answer is "not on DC side"? how to express
that?)
Let's just say "Yes". (Most of) the other IMs also have
size limitations
here.
- No support for voice/video chats, right?
Nope, not yet.
- Read receipts = no, right? I wonder if
someone has thought about
ways to implement this feature for DC already.
Yes, there are read receipts,
they can be turned on in the settings :) - No
editing, nor deleting sent messages, right?
Editing No, Deleting... partial I'd
say? - No
"custom emojis"? (what in earth is that?)
Custom emojis are emojis you can add & edit yourself, I think :) we
don't support that (yet).
- No stickers?
Stickers are almost ready in the desktop client... let's leave that out
for now.
- No self destructing messages, correct?
(that would be awesome, is
currently my #1 needed privacy feature together with no contacts
upload)
Not yet, no... people are thinking about how to best implement
that.
It's hard to force the other side to delete them; especially if they
don't use Delta, but a different E-Mail client. -
Screenshot protection?
Nope.
- Support for themes/skins?
Yes, there
is dark mode :)
- Support for plugins?
Nope.
- No peer to peer text chats.
Nope.
- What to put in "Open source
servers"? "Depends"?
Yes, there are Open Source servers. Whoever
cares about this feature
will use them.