Spam Call Blocker vs ThreatScoopOnionChat
Side-by-side comparison of two open source alternatives
Spam Call Blocker
Call Blocker App helps you manage and block unwanted incoming calls while maintaining a whitelist of approved contacts. It uses web scraping to enhance the call-blocking experience by integrating real-time data from popular spam-detection Spanish websites.Features:Block and Unblock Numbers: Easily block or unblock specific phone numbers.Whitelist Management: Maintain a whitelist of phone numbers that are always allowed to reach you.Web-Based Number Lookup: Automatically look up phone numbers using two trusted Spanish websites:www.listaspam.comwww.responderono.esReal-Time Web Scraping: Leverage web scraping techniques to gather real-time information on whether a number should be blocked.How It WorksThe app uses the JSoup library for web scraping, which allows it to retrieve and parse HTML data from www.listaspam.com and www.responderono.es. This data is then processed to determine whether an incoming call should be blocked or not.Data ManagementExport: Users can export all their preferences, including settings and black/white lists of numbers, to a file for backup or transfer to another device.Import: Previously exported data can be imported, allowing users to quickly set up the app on a new device or restore settings after a reset.Privacy and SecurityThis app is designed with user privacy in mind. All data is stored locally on the device, and the app only accesses the internet to perform web scraping for number lookup. No personal data is shared with external servers.
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 | Spam Call Blocker | ThreatScoopOnionChat |
|---|---|---|
| License | GPL-3.0-only | GPL-3.0-only |
| Install sources | GitHubIzzyOnDroid | F-DroidGitHub |
| Categories | SMSMessaging | SMSMessagingBrowser |
| Features | Ad-FreeOpen SourceNo Tracking | Ad-FreeOpen SourceNo Tracking |
| Platforms | Android | Android |
| Website | ||
| Source code |