privacyguides/privacytools.io
Archived
1
0
Fork 0
Code Issues 304 Pull Requests 47 Activity

add Session messenger + new sub-section for nodal messengers

Browse Source 
Signed-off-by: Stephen L. <lrq3000@gmail.com>
This commit is contained in:
Stephen L 2021-05-15 05:37:08 +02:00
parent 1bc3a98d8d
commit ee915d912e
1 changed files with 43 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
_includes/sections/instant-messenger.html
View File

@ -180,3 +180,46 @@
</div>
</div>
</div>
<div>
<h2 id="nodal" class="anchor">
<a href="#nodal"><i class="fas fa-link anchor-icon"></i></a>
Nodal
</h2>
<p>Nodal networks route encrypted messages through a network of user operated nodes. The nodes cannot decrypt messages, only the recipient can decrypt. Examples of this include <a href="https://en.wikipedia.org/wiki/Onion_routing">Onion routing</a> (used with technologies like <a href="https://en.wikipedia.org/wiki/Tor_(anonymity_network)">Tor</a>) and <a href="https://en.wikipedia.org/wiki/Blockchain">Blockchains</a>. A direct connection is never made, ensuring that the recipient cannot access the sender's metadata (eg, IP address). If the network uses onion routing, then the nodes can't either.</p>
{%
include cardv2.html
title="Session"
image="/assets/img/svg/3rd-party/session.svg"
description="Encrypted instant messenger using 3-hop onion routing to transfer communications. All communications are E2EE encrypted by default, supporting 1-on-1, private group and public group chatrooms."
website="https://getsession.org/"
privacy-policy="https://getsession.org/privacy-policy/"
github="https://github.com/oxen-io/session-desktop"
googleplay="https://play.google.com/store/apps/details?id=network.loki.messenger"
ios="https://apps.apple.com/app/session-private-messenger/id1470168868"
windows="https://getsession.org/windows"
linux="https://www.getsession.org/linux"
mac="https://getsession.org/mac"
%}
<div class="container">
<div class="row">
<div class="col-md-6">
<h3>Advantages</h3>
<ul>
<li>Minimal to no information is exposed to third parties.</li>
<li>Messages can be relayed even if one of the parties is offline.</li>
</ul>
</div>
<div class="col-md-6">
<h3>Disadvantages</h3>
<ul>
<li>Slow transfers and messages propagation.</li>
<li>Less reliable due to the random nodes routing, some nodes may be very far from the sender and receiver, adding latency or even failing to transmit messages if one of the nodes goes offline.</li>
<li>More complex to use as it requires the creation and backup of a private key.</li>
</ul>
</div>
</div>
</div>