Google’s reCAPTCHA service is reportedly broken for users on de-Googled Android devices, raising accessibility and privacy concerns.
Google’s reCAPTCHA service is reportedly broken for users on de-Googled Android devices, raising accessibility and privacy concerns.
Proof or else its just blabla bla
It would be better to prove that it is secure. If you think about last year, for example (That applies to Qualcomm, so you’d have to check what hardware is installed. ) —CVE-2026-25262(But it’s only now making headlines)—the question remains: what hasn’t been discovered yet?
Oh look, grapheneOS was vulnerable… but it’s been fixed now https://discuss.grapheneos.org/d/35355-details-on-the-may-2026-android-security-bulletin (not same CVE)
https://forum.torproject.org/t/enabling-grapheneos-protections-causes-tor-browser-for-android-to-break/21535 lol
The focus is still on what has been discovered; the question remains: what has not yet been discovered?
Ty, for info
No problem. So grapheneOS will definitely prioritize security more than the others. But ultimately, it still relies on hardware that, by its very nature, cannot be trusted. Similarly, even the developers at grapheneOS can make mistakes. Therefore, you should generally view such systems as compromised and not trust them blindly. Then there are also methods like uXDT, where devices communicate with each other via sound (a frequency we cannot hear), and so on. Thats the reason I call it honeypotOS.
I never have 100% confidence in telephony or technology. Have just started with meshcore, reticulum also looks interesting.
Thanks for mentioning that. I haven’t heard of Reticulum before, but it sounds interesting.