Session F-Droid vs ThreatScoopOnionChat
Side-by-side comparison of two open source alternatives
Session F-Droid
This is an unofficial rebrand of Session without Firebase push service so the "fast mode" can't be enabled. If you want to use the "fast mode" please use the official Session client from their own repo. Session is a new breed of encrypted private messenger, built on a unique network of user-operated servers spread all over the world. With no central servers, Session can't leak or sell your data. You don't need a phone number or email to sign up — your Session ID can stay completely anonymous. And Session's private routing protocols keep your messages secret and secure. No one ever knows who you're talking to, what you're saying, or even your IP address. • Fully anonymous account creation, no phone number or email required • Decentralised server network: No data breaches and no central point of failure • No metadata logging: Session doesn't store, track, or log your messaging metadata • IP address protection: Device IP addresses are never exposed to the person you're talking to or the servers holding your data • Closed groups: Private, end-to-end encrypted group chats for up to 100 people • Encrypted attachments: Share voice snippets, photos, and files with Session's security and privacy protections • Free and fully open-source: Don't take our word for it — check Session's code yourself Session is free as in free speech, free as in free beer, and free of ads and trackers. Session is built and maintained by the Loki Foundation, Australia's first privacy tech not-for-profit organisation. Take back your online privacy today — download Session. Want to build from source, report a bug, or just take a look at our code? Check out Session on GitHub: https://github.com/session-foundation/session-android
ThreatScoopOnionChat
# ThreadScoopOnionChat This version is a fork from " https://github.com/session-foundation/session-android ", enfocado en la privacidad. ## How Did ThreadScoopOnionChat Come About? I have always been a fan of privacy and security in communications, and I am constantly researching potential security breaches in messaging applications. ThreadScoopOnionChat emerged after the analysis of this blog "https://soatok.blog/2025/01/14/dont-use-session-signal-fork/", in which several aspects are described as to why using Session is not recommended, and I wondered how it is possible that a foundation focused on privacy—with the grants and support it receives—has not been able to improve this protocol. I still do not understand the answer, since my resources are much smaller than those of a foundation compared to that of a person who is simply a fan of privacy and security. In this blog, certain problems were described: 1> "https://soatok.blog/2025/01/14/dont-use-session-signal-fork/#insufficient-entropy-ed25519" 2> "https://soatok.blog/2025/01/14/dont-use-session-signal-fork/#in-band-negotiation" 3> "https://soatok.blog/2025/01/14/dont-use-session-signal-fork/#public-keys-aes-gcm" This is a forked version privacy focussed from Session. Go Github to check all features implemented.
| Feature | Session F-Droid | ThreatScoopOnionChat |
|---|---|---|
| License | GPL-3.0-only | GPL-3.0-only |
| Install sources | F-DroidGitHub | F-DroidGitHub |
| Categories | SMSMessagingBrowser | SMSMessagingBrowser |
| Features | Ad-FreeOpen SourceNo Tracking | Ad-FreeOpen SourceNo Tracking |
| Platforms | Android | Android |
| Website | ||
| Source code |