baresip+ vs ThreatScoopOnionChat
Side-by-side comparison of two open source alternatives
baresip+
This is a baresip based SIP and mobile calling and messaging User Agent for Android. Currently baresip+ supports SIP and mobile based voice calls and messages as well as SIP based video calls. In addition, voice conference calls, voicemail Message Waiting Indication as well as blind and attended call transfers are available when SIP is used. MMS messaging is not supported yet. In SIP calls audio can be coded with Opus, AMR, Codec2, G.729, G.722, G.722.1, or PCMU/PCMA codecs. Video can be coded with VP9, VP8, H.265, H.264, or AV1 codecs. Security is achieved via TLS or WSS SIP signaling transport and ZRTP or (DTLS) SRTP media encapsulation. Development of baresip+ is motivated by need for a secure, open source SIP based VoIP User Agent for Android that does not depend on proprietary, third party push notification services. Contacts, mobile calling, and SMS messaging were added in order to reduce app pollution. This application can be installed on Android devices running Android version 9 or later. Mobile calling and messaging needs Android version 10 or later. If you don't need video calling, you can instead of this app install its lighter weight sister app baresip. Source code is available at GitHub, where also issues can be reported.
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 | baresip+ | ThreatScoopOnionChat |
|---|---|---|
| License | BSD-3-Clause | 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 |