From 7c66d26061e82fbafefb59f6059562cae35b512f Mon Sep 17 00:00:00 2001 From: jermanuts <109705802+jermanuts@users.noreply.github.com> Date: Thu, 11 Apr 2024 19:16:19 +0300 Subject: [PATCH] update: More detailed Session description (#2519) Signed-off-by: fria <138676274+friadev@users.noreply.github.com> Signed-off-by: redoomed1 <161974310+redoomed1@users.noreply.github.com> Co-Authored-By: Jonah Aragon --- docs/real-time-communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/real-time-communication.md b/docs/real-time-communication.md index e0ea1cae5f..becd3be3b2 100644 --- a/docs/real-time-communication.md +++ b/docs/real-time-communication.md @@ -251,7 +251,7 @@ Session uses the decentralized [Oxen Service Node Network](https://oxen.io) to s -Session allows for E2EE in one-on-one chats or closed groups which allow for up to 100 members. Open groups have no restriction on the number of members, but are open by design. +Session allows for E2EE in one-on-one chats or closed groups which allow for up to 100 members. It is also possible to [set up](https://docs.oxen.io/oxen-docs/products-built-on-oxen/session/guides/open-group-setup) or join open groups which can host thousands of members, but messages in these open groups are **not** end-to-end encrypted between participants. Session was previously based on Signal Protocol before replacing it with their own in December 2020. Session Protocol does [not](https://getsession.org/blog/session-protocol-technical-information) support forward secrecy.[^1]