4 Jan
2020
4 Jan
'20
6:26 p.m.
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 things might
need some collective thinking.
- All other entries have their own Wikipedia page. Might this be a
blocker? Have you considered creating one?
- Who should be listed as "Developer"? Is there such a thing as
copyright for the code and/or brand?
- When was the first public release?
- Is there a count of "monthly active users"?
- 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?
- I guess the license can be pulled from github, but if there are
any gotchas it might be good to know.
- Support for which operating systems should be listed as "Yes"?
- How to express that there is E2EE only after the first message?
How does that work exactly for group messages?
- 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?)
- No support for voice/video chats, right?
- Read receipts = no, right? I wonder if someone has thought about
ways to implement this feature for DC already.
- No editing, nor deleting sent messages, right?
- No "custom emojis"? (what in earth is that?)
- No stickers?
- No self destructing messages, correct? (that would be awesome, is
currently my #1 needed privacy feature together with no contacts
upload)
- Screenshot protection?
- Support for themes/skins?
- Support for plugins?
- No peer to peer text chats.
- What to put in "Open source servers"? "Depends"?
- Is "Yes" a sane answer for "Federated servers"?
Many details needed!