We survived for three years without funding. Help us keep rolling →Unplug friends from Signal with one link →New listings: Cock.li, Proton, Disroot →

home / messaging

Session

freedom tech 8
decentralizedpermissionlessopen-sourceno accountno phone numberno email addressself-custodystrong metadata protectione2eeunique usernameimmutable eventsno PFSpoor tokenomicsno community appsno self-hostingcompliant teamhostile jurisdictiontoken2020

PFS

Since Session lacks perfect-forward secrecy (PFS) and therefore does not rotate encryption keys, a compromised key can be used to decrypt every message in a chat. PFS is planned for Session V2.

File sharing

By default, attachments (images, audio, video, other files) are routed through centralized servers operated by an officially registered compliant company based in a hostile jurisdiction, rather than Session swarms. While file encryption and 3-hop routing persist, offloading attachments to these centralized servers weakens privacy and significantly increases exposure to "harvest now, decrypt later" threats.

Multi-account

Official Session apps don't support multiple accounts, so users are bound to one identity. This limitation can be circumvented by launching an app via command line with a custom account path:

session.AppImage --user-data-dir=/path/to/account/dir

Groups

Default Session group chats support up to 100 members max and don't provide an invite link, so each user should be added manually. For larger communities, it's necessary to host a Session Open Group Server (SOGS) which comes with an invite link that can be used to join the group chat.

Forum:

Official:

Useful:

Community:

Send a message to darkvegas to request an invite to our private Session group.