
ThreatScoopOnionChat
A Forked Version focused on privacy from SESSION
# 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.
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.
Anti-Features
This app has features you may not like. Learn more!
- Author: R00tedBrain
- License: GNU General Public License v3.0 only
- Website
- Issue Tracker
- Translation
- Source Code
- Changelog
- Build Metadata
Versions
Although APK downloads are available below to give you the choice, you should be aware that by installing that way you will not receive update notifications and it's a less secure way to download. We recommend that you install the F-Droid client and use that.
Download F-Droid-
arm64-v8a
armeabi
armeabi-v7a
mips
mips64
x86
x86_64
This version requires Android 8.0 or newer.
It is built by F-Droid and guaranteed to correspond to this source tarball.
Download APK 131 MiB PGP Signature | Build Log