# CloudflareCDN 0click location deanonymization attack targeting Signal, Discord and other platforms

**URL:** https://discuss.privacyguides.net/t/cloudflarecdn-0click-location-deanonymization-attack-targeting-signal-discord-and-other-platforms/24244
**Category:** General
**Created:** 2025-01-21T16:11:51Z
**Posts:** 20
**Showing post:** 18 of 20

## Post 18 by @jerm — 2025-01-21T22:18:35Z

Well, I don’t agree with most of their excuses about not implementing some feature due to X reasons, take for example, local database encryption. Moxie (ex-signal dev) didn’t want to implement it because he believed that “it will be stored in memory forever at first unlock”, but [Molly](https://molly.im/) dev proved [him wrong](https://discuss.grapheneos.org/d/8976-signal-vs-molly-vs-molly-foss/7). There are multiple features that Signal just refuses to implement when it is entirely possible and will vastly improve user’s privacy or security.

Molly kept adding such [features](https://molly.im/#features) while Signal deliberately didn’t do anything remarkable at all other than cryptography (which I respect btw), it is just a part of what makes messenger secure, there are a lot of other attack vectors you should be putting into account and mitigate when you are providing people with a whole instant messaging app and not just providing cryptographic primitives.

Here’s a list of what features Molly have & going to have: [Recommend Molly alongside Signal - #11 by jerm](https://discuss.privacyguides.net/t/recommend-molly-alongside-signal/17597/11).

---

_[View the full topic](https://discuss.privacyguides.net/t/cloudflarecdn-0click-location-deanonymization-attack-targeting-signal-discord-and-other-platforms/24244)._