Post #2429277

2026-04-10 13:58 UTC

@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.

Replies (2)

@GrapheneOS@grapheneos.social 2026-04-10 14:01

@projetslibres_podcast@piaille.fr @Framasoft@framapiaf.org @fla@mastodon.social Exodus Privacy uses a very similar approach to label apps as having trackers based on whether they include a library from a small list they've decided as trackers. Many of those decisions are dubious and it misses that the most privacy invasive behavior by apps isn't done that way. It also has extremely inaccurate labelling of permissions misleading users about how that works. Here's a great example of both with Facebook Lite: https://reports.exodus-privacy.eu.org/en/reports/com.facebook.lite/latest/

Open ##2429278
@Byte@rage.love 2026-04-10 14:11

@GrapheneOS@grapheneos.social My hot take is that closed source software shouldn’t be allowed to do DNS over HTTPS, or perhaps even make arbitrary network requests at all Granted, I use Steam for video games all the time and the majority of the client is closed source and proprietary. The most important difference there I guess is that I actually trust Valve.

Open ##2429281