Post #2429276

2026-04-10 13:51 UTC

@projetslibres_podcast@piaille.fr @Framasoft@framapiaf.org @fla@mastodon.social /e/ tries to provide privacy by bundling a small blocklist of domain names solely used for ads and analytics. This doesn't do anything to address the most privacy invasive behavior by apps which happens via their own services. It doesn't stop apps sending data to arbitrary third parties from their servers or even client side. It can't block anything without the app using a dedicated domain for the unwanted behavior which usually isn't how things are done.

Replies (2)

@GrapheneOS@grapheneos.social 2026-04-10 13:58

@projetslibres_podcast@piaille.fr @Framasoft@framapiaf.org @fla@mastodon.social The domains they block are a tiny subset of domains used for those purposes and do not stop the most privacy invasive behavior by apps. Apps and SDKs have also increasingly bypassed DNS blocklists via DNS-over-HTTPS resolvers, hard-wired IP addresses and most of all moving connecting to third party APIs to their servers where they don't need to leak their API keys. DNS filtering works fine on GrapheneOS but isn't a viable approach to protecting privacy.

Open ##2429277
@Okuna@social.tchncs.de 2026-04-10 14:11

@GrapheneOS@grapheneos.social @projetslibres_podcast@piaille.fr @Framasoft@framapiaf.org @fla@mastodon.social I think it's consequent to only have a small block list because if they would have a bigger one which blocks more invasive trackers, and more security they couldn't claim that your system is only for pedophiles. My 10 cent The interviews from the CEO of /e/os basically state that they can't take security and privacy serious. Else they would contradict themselves and that makes the entire system a half-hearted approach.

Open ##2429282