|
|
|
@ -1,4 +1,7 @@
|
|
|
|
<h1 id="im" class="anchor"><a href="#im"><i class="fas fa-link anchor-icon"></i></a> Encrypted Instant Messengers</h1>
|
|
|
|
<h1 id="im" class="anchor">
|
|
|
|
|
|
|
|
<a href="#im"><i class="fas fa-link anchor-icon"></i></a>
|
|
|
|
|
|
|
|
Encrypted Instant Messengers
|
|
|
|
|
|
|
|
</h1>
|
|
|
|
|
|
|
|
|
|
|
|
<div class="alert alert-warning" role="alert">
|
|
|
|
<div class="alert alert-warning" role="alert">
|
|
|
|
<strong>If you are currently using an Instant Messenger like Telegram, LINE, Viber, <a href="https://www.eff.org/deeplinks/2016/10/where-whatsapp-went-wrong-effs-four-biggest-security-concerns">WhatsApp</a>, or plain SMS, you should pick an alternative here.</strong></div>
|
|
|
|
<strong>If you are currently using an Instant Messenger like Telegram, LINE, Viber, <a href="https://www.eff.org/deeplinks/2016/10/where-whatsapp-went-wrong-effs-four-biggest-security-concerns">WhatsApp</a>, or plain SMS, you should pick an alternative here.</strong></div>
|
|
|
|
@ -9,27 +12,13 @@
|
|
|
|
|
|
|
|
|
|
|
|
<p>We have described the three main types of messaging programs that exist: Centralized, Federated and Peer-to-Peer (P2P), with the advantages and disadvantages of each.</p>
|
|
|
|
<p>We have described the three main types of messaging programs that exist: Centralized, Federated and Peer-to-Peer (P2P), with the advantages and disadvantages of each.</p>
|
|
|
|
|
|
|
|
|
|
|
|
<h2 id="centralized" class="anchor"><a href="#centralized"><i class="fas fa-link anchor-icon"></i></a> Centralized</h2>
|
|
|
|
<h2 id="centralized" class="anchor">
|
|
|
|
|
|
|
|
<a href="#centralized"><i class="fas fa-link anchor-icon"></i></a>
|
|
|
|
|
|
|
|
Centralized
|
|
|
|
|
|
|
|
</h2>
|
|
|
|
|
|
|
|
|
|
|
|
<p>Centralized messengers are those where every participant is on the same server or network of servers controlled by the same organization.</p>
|
|
|
|
<p>Centralized messengers are those where every participant is on the same server or network of servers controlled by the same organization.</p>
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Advantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>New features and changes can be implemented more quickly.</li>
|
|
|
|
|
|
|
|
<li>Easier to get started with and to find contacts.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Disadvantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Centralized services could be more susceptible to <a href="#exploiting-centralized-networks">legislation requiring backdoor access</a>.</li>
|
|
|
|
|
|
|
|
<li>Can include <a href="https://drewdevault.com/2018/08/08/Signal.html">restricted control or access</a>. This can include things like:</li>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Being <a href="https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165">forbidden from connecting third-party clients</a> to the centralized network that might provide for greater customization or better user experience. Often defined in Terms and Conditions of usage.</li>
|
|
|
|
|
|
|
|
<li>Poor or no documentation for third-party developers.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<li>The <a href="https://blog.privacytools.io/delisting-wire">ownership</a>, privacy policy, and operations of the service can change easily when a single entity controls it, potentially compromising the service later on.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{%
|
|
|
|
{%
|
|
|
|
include cardv2.html
|
|
|
|
include cardv2.html
|
|
|
|
title="Signal"
|
|
|
|
title="Signal"
|
|
|
|
@ -67,37 +56,45 @@
|
|
|
|
chrome="https://chrome.google.com/webstore/detail/keybase-for-reddit/ognfafcpbkogffpmmdglhbjboeojlefj"
|
|
|
|
chrome="https://chrome.google.com/webstore/detail/keybase-for-reddit/ognfafcpbkogffpmmdglhbjboeojlefj"
|
|
|
|
%}
|
|
|
|
%}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<div class="container">
|
|
|
|
|
|
|
|
<div class="row">
|
|
|
|
|
|
|
|
<div class="col-md-6">
|
|
|
|
|
|
|
|
<h3>Advantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>New features and changes can be implemented more quickly.</li>
|
|
|
|
|
|
|
|
<li>Easier to get started with and to find contacts.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
<div class="col-md-6">
|
|
|
|
|
|
|
|
<h3>Disadvantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Centralized services could be more susceptible to <a href="#exploiting-centralized-networks">legislation requiring backdoor access</a>.</li>
|
|
|
|
|
|
|
|
<li>Can include <a href="https://drewdevault.com/2018/08/08/Signal.html">restricted control or access</a>. This can include things like:</li>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Being <a href="https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165">forbidden from connecting third-party clients</a> to the centralized network that might provide for greater customization or better user experience. Often defined in Terms and Conditions of usage.</li>
|
|
|
|
|
|
|
|
<li>Poor or no documentation for third-party developers.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<li>The <a href="https://blog.privacytools.io/delisting-wire">ownership</a>, privacy policy, and operations of the service can change easily when a single entity controls it, potentially compromising the service later on.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<div>
|
|
|
|
<div>
|
|
|
|
<h2 id="federated" class="anchor"><a href="#federated"><i class="fas fa-link anchor-icon"></i></a> Federated</h2>
|
|
|
|
<h2 id="federated" class="anchor">
|
|
|
|
|
|
|
|
<a href="#federated"><i class="fas fa-link anchor-icon"></i></a>
|
|
|
|
|
|
|
|
Federated
|
|
|
|
|
|
|
|
</h2>
|
|
|
|
|
|
|
|
|
|
|
|
<p>Federated messengers use multiple, independent servers that are able to talk to each other (email is one example of a federated service). Federation allows system administrators to control their own server and still be a part of the larger communications network.</p>
|
|
|
|
<p>Federated messengers use multiple, independent servers that are able to talk to each other (email is one example of a federated service). Federation allows system administrators to control their own server and still be a part of the larger communications network.</p>
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Advantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Allows for greater control over your own data when running your own server.</li>
|
|
|
|
|
|
|
|
<li>Allows you to choose who to trust your data with by choosing between multiple "public" servers.</li>
|
|
|
|
|
|
|
|
<li>Often allows for third party clients which can provide a more native, customized, or accessible experience.</li>
|
|
|
|
|
|
|
|
<li>Generally a less juicy target for governments wanting <a href="#exploiting-centralized-networks">backdoor access to everything</a> as the trust is decentralized. The server may be hosted independently from the organization developing the software.</li>
|
|
|
|
|
|
|
|
<li>Server software can be verified that it matches public source code, assuming you have access to the server or you trust the person who does (e.g., a family member)</li>
|
|
|
|
|
|
|
|
<li>Third-party developers can contribute code and add new features, instead of waiting for a private development team to do so.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Disadvantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Adding new features is more complex, because these features need to be standardized and tested to ensure they work with all servers on the network.</li>
|
|
|
|
|
|
|
|
<li>Some metadata may be available (e.g., information like "who is talking to whom," but not actual message content if E2EE is used).</li>
|
|
|
|
|
|
|
|
<li>Federated servers generally require trusting your server's administrator. They may be a hobbyist or otherwise not a "security professional," and may not serve standard documents like a privacy policy or terms of service detailing how your data is utilized.</li>
|
|
|
|
|
|
|
|
<li>Server administrators sometimes choose to block other servers, which are a source of unmoderated abuse or break general rules of accepted behavior. This will hinder your ability to communicate with users on those servers.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{%
|
|
|
|
{%
|
|
|
|
include cardv2.html
|
|
|
|
include cardv2.html
|
|
|
|
title="Matrix"
|
|
|
|
title="Riot"
|
|
|
|
image="/assets/img/svg/3rd-party/matrix.svg"
|
|
|
|
image="/assets/img/svg/3rd-party/riotim.svg"
|
|
|
|
image-dark="/assets/img/svg/3rd-party/matrix-dark.svg"
|
|
|
|
description='<a href="//about.riot.im">Riot.im</a> is the reference client for the <a href="//matrix.org/docs/guides/introduction">Matrix</a> network. The <a href="//matrix.org/docs/spec">Matrix open standard</a> is an open-source standard for secure, decentralized, real-time communication.<br />'
|
|
|
|
description='<a href="https://matrix.org/docs/guides/introduction">Matrix</a> is an open-source project that publishes the <a href="https://matrix.org/docs/spec">Matrix open standard</a> for secure, decentralized, real-time communication.<br />
|
|
|
|
labels="warning:<a href=//github.com/vector-im/riot-web/issues/6779>Warning</a>:Riot offers optional E2EE for 1:1 and group conversations that must be turned on by the user.
|
|
|
|
<a href="https://en.wikipedia.org/wiki/Riot.im">Riot.im</a> is the popular reference client produced by the Matrix.org team. It offers optional E2EE for 1:1 and group conversations that <strong>must</strong> be turned on by the user. (This can be done by clicking on the toggle switch which is accessed by clicking the room name or user name of the chat → Security & Privacy → Encrypted). In the future it will be <a href="https://github.com/vector-im/riot-web/issues/6779">on by default.</a>'
|
|
|
|
(This can be done by clicking on the toggle switch which is accessed by clicking the room name or user name of the chat → Security & Privacy → Encrypted).|success:VoIP"
|
|
|
|
website="https://about.riot.im/"
|
|
|
|
website="https://about.riot.im/"
|
|
|
|
forum="https://forum.privacytools.io/t/discussion-riot-im/665/"
|
|
|
|
forum="https://forum.privacytools.io/t/discussion-riot-im/665/"
|
|
|
|
github="https://github.com/vector-im/riot-web/"
|
|
|
|
github="https://github.com/vector-im/riot-web/"
|
|
|
|
@ -110,42 +107,44 @@
|
|
|
|
web="https://riot.im/app/"
|
|
|
|
web="https://riot.im/app/"
|
|
|
|
%}
|
|
|
|
%}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<div class="container">
|
|
|
|
|
|
|
|
<div class="row">
|
|
|
|
|
|
|
|
<div class="col-md-6">
|
|
|
|
|
|
|
|
<h3>Advantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Allows for greater control over your own data when running your own server.</li>
|
|
|
|
|
|
|
|
<li>Allows you to choose who to trust your data with by choosing between multiple "public" servers.</li>
|
|
|
|
|
|
|
|
<li>Often allows for third party clients which can provide a more native, customized, or accessible experience.</li>
|
|
|
|
|
|
|
|
<li>Generally a less juicy target for governments wanting <a href="#exploiting-centralized-networks">backdoor access to everything</a> as the trust is decentralized. The server may be hosted independently from the organization developing the software.</li>
|
|
|
|
|
|
|
|
<li>Server software can be verified that it matches public source code, assuming you have access to the server or you trust the person who does (e.g., a family member)</li>
|
|
|
|
|
|
|
|
<li>Third-party developers can contribute code and add new features, instead of waiting for a private development team to do so.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
<div class="col-md-6">
|
|
|
|
|
|
|
|
<h3>Disadvantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Adding new features is more complex, because these features need to be standardized and tested to ensure they work with all servers on the network.</li>
|
|
|
|
|
|
|
|
<li>Some metadata may be available (e.g., information like "who is talking to whom," but not actual message content if E2EE is used).</li>
|
|
|
|
|
|
|
|
<li>Federated servers generally require trusting your server's administrator. They may be a hobbyist or otherwise not a "security professional," and may not serve standard documents like a privacy policy or terms of service detailing how your data is utilized.</li>
|
|
|
|
|
|
|
|
<li>Server administrators sometimes choose to block other servers, which are a source of unmoderated abuse or break general rules of accepted behavior. This will hinder your ability to communicate with users on those servers.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<div>
|
|
|
|
<div>
|
|
|
|
<h4>Worth Mentioning</h4>
|
|
|
|
<h4>Worth Mentioning</h4>
|
|
|
|
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
<ul>
|
|
|
|
<li>Other <a href="https://matrix.org/clients">Matrix</a> clients, that may however be less feature complete than Riot.im.</li>
|
|
|
|
<li><a href="https://status.im">Status.im</a> - Encrypted instant messenger with an integrated <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a> wallet (cryptocurrency) that also includes support for <a href="https://our.status.im/tag/dapps">DApps (decentralized apps)</a> (web apps in a curated store). Uses the <a href="https://our.status.im/status-launches-private-peer-to-peer-messaging-protocol/">Waku protocol (a fork of Whisper)</a> for P2P communication. Only available for iOS and Android.</li>
|
|
|
|
<li><a href="https://xmpp.org/about">XMPP</a> (Extensible Messaging and Presence Protocol) is an open-source communications protocol that began development in 1999. Since then, XMPP has been extended by the publishing of XEPs (XMPP Extension Protocols). <a href="https://conversations.im/omemo/">OMEMO</a> is the most popular XEP (XMPP extension) for E2EE. Clients are developed by the community and not by the XSF (XMPP Standards Foundation). <span class="badge badge-warning" data-toggle="tooltip" title="VoIP and file transfers/names may not be end-to-end encrypted.">Inconsistent E2EE</span></li>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li><a href="https://gajim.org/">Gajim</a></li>
|
|
|
|
|
|
|
|
<li><a href="https://conversations.im">Conversations</a></li>
|
|
|
|
|
|
|
|
<li><a href="https://siskin.im/">Siskin</a></li>
|
|
|
|
|
|
|
|
<li>Other <a href="https://omemo.top">OMEMO</a> capable clients for XMPP.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<li><a href="https://www.kontalk.org">Kontalk</a> is a community-driven instant messaging network based on XMPP.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
<h2 id="peer-to-peer" class="anchor"><a href="#peer-to-peer"><i class="fas fa-link anchor-icon"></i></a> Peer to Peer (P2P)</h2>
|
|
|
|
<h2 id="peer-to-peer" class="anchor">
|
|
|
|
|
|
|
|
<a href="#peer-to-peer"><i class="fas fa-link anchor-icon"></i></a>
|
|
|
|
|
|
|
|
Peer to Peer (P2P)
|
|
|
|
|
|
|
|
</h2>
|
|
|
|
|
|
|
|
|
|
|
|
<p>Peer-to-Peer instant messengers connect directly to each other without requiring third-party servers. Clients (peers) usually find each other through the use of a <a href="https://en.wikipedia.org/wiki/Distributed_computing">distributed computing</a> network. Examples of this include <a href="https://en.wikipedia.org/wiki/Distributed_hash_table">DHT (distributed hash table)</a> (used with technologies like <a href="https://en.wikipedia.org/wiki/BitTorrent_(protocol)">torrents</a> and <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a>, for example), or <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a>'s <a href="https://github.com/ethereum/wiki/wiki/Whisper">Whisper</a> protocol (used with some newer DApps). Another approach is proximity based networks, where a connection is established over WiFi or Bluetooth (for example, Briar or the <a href="https://www.scuttlebutt.nz">Scuttlebutt</a> social networking protocol). Once a peer has found a route to its contact via any of these methods, a direct connection between them is made.</p>
|
|
|
|
<p>Peer-to-Peer instant messengers connect directly to each other without requiring third-party servers. Clients (peers) usually find each other through the use of a <a href="https://en.wikipedia.org/wiki/Distributed_computing">distributed computing</a> network. Examples of this include <a href="https://en.wikipedia.org/wiki/Distributed_hash_table">DHT (distributed hash table)</a> (used with technologies like <a href="https://en.wikipedia.org/wiki/BitTorrent_(protocol)">torrents</a> and <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a>, for example). Another approach is proximity based networks, where a connection is established over WiFi or Bluetooth (for example, Briar or the <a href="https://www.scuttlebutt.nz">Scuttlebutt</a> social networking protocol). Once a peer has found a route to its contact via any of these methods, a direct connection between them is made.</p>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Advantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Minimal information is exposed to third parties.</li>
|
|
|
|
|
|
|
|
<li>Modern P2P platforms implement end-to-end encryption by default. There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3>Disadvantages</h3>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Reduced feature set:</li>
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li>Messages can only be sent when both peers are online, however, your client may store messages locally to wait for the contact to return online.</li>
|
|
|
|
|
|
|
|
<li>Generally increases battery usage on mobile devices, because the client must stay connected to the distributed network to learn about who is online.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<li>Your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and that of the contacts you're communicating with may be visible if you do not use the software in conjunction with a <a href="/software/networks">self contained network</a>, such as <a href="https://www.torproject.org">Tor</a> or <a href="https://geti2p.net/">I2P</a>. Many countries have some form of mass surveillance and/or metadata retention.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{%
|
|
|
|
{%
|
|
|
|
include cardv2.html
|
|
|
|
include cardv2.html
|
|
|
|
@ -176,30 +175,25 @@
|
|
|
|
ios="https://itunes.apple.com/app/ring-a-gnu-package/id1306951055?mt=8"
|
|
|
|
ios="https://itunes.apple.com/app/ring-a-gnu-package/id1306951055?mt=8"
|
|
|
|
%}
|
|
|
|
%}
|
|
|
|
|
|
|
|
|
|
|
|
{%
|
|
|
|
<div class="container">
|
|
|
|
include cardv2.html
|
|
|
|
<div class="row">
|
|
|
|
title="Tox"
|
|
|
|
<div class="col-md-6">
|
|
|
|
image="/assets/img/svg/3rd-party/tox.svg"
|
|
|
|
<h3>Advantages</h3>
|
|
|
|
image-dark="/assets/img/svg/3rd-party/tox-dark.svg"
|
|
|
|
<ul>
|
|
|
|
description='Encrypted instant messaging and video calling software. Uses its <a href="https://toktok.ltd/spec.html"> own encryption protocol</a> that has not yet been officially audited by cryptographers.'
|
|
|
|
<li>Minimal information is exposed to third parties.</li>
|
|
|
|
labels="warning:<a href=//tox.chat/download.html#warning>Experimental</a>:Encryption has not been audited by professional cryptographers|success:VoIP"
|
|
|
|
<li>Modern P2P platforms implement end-to-end encryption by default. There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models.</li>
|
|
|
|
website="https://tox.chat"
|
|
|
|
</ul>
|
|
|
|
forum="https://forum.privacytools.io/t/discussion-tox/2115"
|
|
|
|
</div>
|
|
|
|
windows="https://tox.chat/download.html#oses"
|
|
|
|
<div class="col-md-6">
|
|
|
|
mac="https://tox.chat/download.html#oses"
|
|
|
|
<h3>Disadvantages</h3>
|
|
|
|
linux="https://tox.chat/download.html#oses"
|
|
|
|
<ul>
|
|
|
|
freebsd="https://tox.chat/download.html#oses"
|
|
|
|
<li>Reduced feature set:</li>
|
|
|
|
openbsd="http://openports.se/search.php?so=tox"
|
|
|
|
<ul>
|
|
|
|
netbsd="http://pkgsrc.se/search.php?so=tox"
|
|
|
|
<li>Messages can only be sent when both peers are online, however, your client may store messages locally to wait for the contact to return online.</li>
|
|
|
|
fdroid="https://tox.chat/download.html#oses"
|
|
|
|
<li>Generally increases battery usage on mobile devices, because the client must stay connected to the distributed network to learn about who is online.</li>
|
|
|
|
googleplay="https://tox.chat/download.html#oses"
|
|
|
|
</ul>
|
|
|
|
ios="https://tox.chat/download.html#oses"
|
|
|
|
<li>Your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and that of the contacts you're communicating with may be visible if you do not use the software in conjunction with a <a href="/software/networks">self contained network</a>, such as <a href="https://www.torproject.org">Tor</a> or <a href="https://geti2p.net/">I2P</a>. Many countries have some form of mass surveillance and/or metadata retention.</li>
|
|
|
|
%}
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
<h4>Worth Mentioning</h4>
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
<ul>
|
|
|
|
|
|
|
|
<li><a href="https://status.im">Status.im</a> - Encrypted instant messenger with an integrated <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a> wallet (cryptocurrency) that also includes support for <a href="https://our.status.im/tag/dapps">DApps (decentralized apps)</a> (web apps in a curated store). Uses the <a href="https://blog.enuma.io/update/2018/08/08/decentralized-application-messaging-with-whisper.html">Whisper protocol</a> for P2P communication. <span class="badge badge-warning">Experimental</span></li>
|
|
|
|
|
|
|
|
<li><a href="https://retroshare.cc">Retroshare</a> - Encrypted instant messaging and voice/video call client. RetroShare supports both <a href="https://www.torproject.org/">Tor</a> and <a href="https://geti2p.net">I2P</a>.</li>
|
|
|
|
|
|
|
|
<li><a href="https://bitmessage.org">Bitmessage</a> is a decentralized, encrypted, peer-to-peer, trustless communications protocol that can be used by one person to send encrypted messages to another person, or to multiple subscribers.</li>
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
