3 ms·
> What's the next step? Imho one thing that the Signal project suffers from -- and that a lot of open-source projects suffer from -- is poor documentation. The
by davorb 11y ago
> What's the next step?
Imho one thing that the Signal project suffers from -- and that a lot of open-source projects suffer from -- is poor documentation. They need document their protocol better, to make it easier for third parties to integrate with their system.
Signal still lacks a working desktop client (no, the one that you can use if you're running Chrome doesn't count), and I'm sure tons of people would be eager to do stuff like provide integration for Pidgin if only there was better documentation.
- ge0rg 11y ago+1 for documentation. The XMPP community is trying to get "OMEMO"[0,1] rolled out, which is an XMPP adaptation of Axolotl, but fails due to missing specs[2]. [0] https://conversations.im/omemo/ https://conversations.im/omemo/ [1] https://conversations.im/xeps/multi-end.html https://conversations.im/xeps/multi-end.html [2] http://mail.jabber.org/pipermail/standards/2015-November/030622.html http://mail.jabber.org/pipermail/standards/2015-November/030...
- Spakman 11y agoI agree about the documentation and a number of other things, but why doesn't the Chromium extension count as a desktop client? You don't need to use Chromium for anything else if you don't want.
- ge0rg 11y agoI suppose the main reason is that it links to your existing Signal installation on iOS/Android, and does not work standalone.