On 04.01.20 19:26, drebs wrote:
compl4xx <compl4xx(a)systemli.org> writes:
Sounds like a great idea :) Do you want to just
add it directly?
I can help, but I don't have all the info needed, and some
need some collective thinking.
- All other entries have their own Wikipedia page. Might this be a
blocker? Have you considered creating one?
I don't know whether anyone
ever tried creating one; it most certainly
makes sense to submit a draft. I'll put it on my list :) But it
shouldn't be a blocker.
- Who should be listed as "Developer"?
Is there such a thing as
copyright for the code and/or brand?
At GitHub, it says "Delta Chat
contributors" everywhere. It's
copyrighted as GPLv3+ (not sure if this is correct, legal stuff is
hard). I'd just go with "Delta Chat contributors".
- When was the first public release?
first GitHub release was on August 14, 2018:
- Is there a count of "monthly active
No. There is no way to measure this. Hm, we could ask the NSA?^^
just leave out the number, many other messengers don't have it either.
- How to succintly express that no specific
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
- 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
- How to express that there is E2EE only after the
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
Let's just say "Yes". (Most of) the other IMs also have
- 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
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
- No self destructing messages, correct? (that
would be awesome, is
currently my #1 needed privacy feature together with no contacts
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?
- Support for themes/skins?
Yes, there is
dark mode :)
- Support for plugins?
- No peer to peer text chats.
- What to put in "Open source servers"?
Yes, there are Open Source servers. Whoever cares about this
will use them.
- Is "Yes" a sane answer for
Yes, very much so. Federation is the great thing
about E-Mail, that it's
the biggest federated network of the world ;)
Many details needed!
I hope this helped, and was also informative for you :) Thanks for your