privacyguides.org/_includes/sections/teamchat.html
Mikaela Suomalainen 1947b84dcf Real time communication improvements (#1147)
* voice-video-messenger: remove duplicates with instant-messenger

also move Tox and Jami to Instant Messengers, Change Jitsi to Jitsi Meet

* instant-messenger: remove platforms of Signal Desktop

https://github.com/privacytoolsIO/privacytools.io/issues/967#issuecomment-520268788

* instant-messenger: add indepedent security audits

* voice-video-messenger: mention that many are already listed above

* instant-messenger: fix formatting & mention features of Jami

* voice-video-messenger: list Mumble

* update source_code.md

* voice-video-messenger: fix card

* add Mumble.png

* Small revisions to the instant messengers

* Spelling!

* voice-video-messenger: add a warning on Jitsi Meet WebRTC

* instant-messenger: remove a from Jami

* instant-messenger: add VoIP badges

* Use updated label functionality

The labels/badges functionality added to cardv2.html in cbe5de4cc2d13d593b5f6d039a236a8b85fe0edd work better here.

* Fix Jitsi Meet warning badge
2019-08-16 21:33:32 -05:00

44 lines
2.4 KiB
HTML

<h1 id="teamchat" class="anchor"><a href="#teamchat"><i class="fas fa-link anchor-icon"></i></a> Team Chat Platforms</h1>
<div class="alert alert-warning" role="alert">
<strong>If your project or organization currently uses a platform like <a href="https://web.archive.org/web/20171029114027/https://feedback.discordapp.com/forums/326712-discord-dream-land/suggestions/17094256-implement-whispersystems-encryption-for-voice-and">Discord</a> or <a href="https://drewdevault.com/2015/11/01/Please-stop-using-slack.html">Slack</a> you should pick an alternative here.</strong>
</div>
{% include cardv2.html
title="Rocket.chat"
image="/assets/img/tools/rocket.chat.png"
description="Rocket.chat is an self-hostable open source platform for team communication. It has optional federation and experimental E2EE."
labels="warning:<a href=//rocket.chat/docs/user-guides/end-to-end-encryption/>Experimental</a>:Regarding E2EE their documentation states 'This feature is currently in alpha. It's also not yet supported on mobile'. There is no forward secrecy so compromised decryption password would leak all messages. The federation was also added afterwards potentially causing room for mistakes."
website="https://rocket.chat/"
forum="https://forum.privacytools.io/t/discussion-rocket-chat/1223"
github="https://github.com/rocketchat/"
android=""
ios=""
mac=""
windows=""
linux=""
%}
{% include cardv2.html
title="Keybase"
image="/assets/img/tools/keybase.png"
description='Keybase provides a hosted team chat with end-to-end encryption. It has also been <a href="https://keybase.io/docs-assets/blog/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf">indepedently audited (PDF)</a>.'
labels="warning:<a href=//github.com/keybase/client/issues/6374>Experimental</a>:The server side of Keybase runs on proprietary code and is centralized."
website="https://keybase.io/"
forum="https://forum.privacytools.io/t/discussion-keybase/1224"
github="https://github.com/Keybase"
android=""
ios=""
mac=""
windows=""
linux=""
web=""
%}
<h3>Worth Mentioning</h3>
<ul>
<li><a href="https://wire.com/en/products/pro-secure-team-collaboration/">Wire Pro</a> - Paid team communication with E2EE. <span class="badge badge-warning" data-toggle="tooltip" title="While the free edition of Wire is a recommended platform, we have not tested the Pro edition.">Untested <i class="far fa-question-circle"></i></span></li>
</ul>