Post #493468

2026-03-02 14:58 UTC

Of course, no question that with threat modeling you can arrive at /e/OS being an acceptable choice. However threat modeling is difficult and the devil is in the details, which is why I’m responding (mostly for the benefit of other readers of this thread) to provide the GrapheneOS side of things and avoid the impression that /e/OS offers unique or generally superior features in the areas we are discussing. Here is GrapheneOS’s network location implementation details. grapheneos.org/features#network-location

Replies (1)

@skarn@discuss.tchncs.de 2026-03-02 20:12

First a technical thing which is not obvious to me. I understand that the general, non-proprietary Android system service would uses a privacy preserving service like BeaconDB. From what I understand, Google offers an alternative, proprietary, location API in its Play Services. Is that one also prevented from giving your location to Google of you’re using Sandboxed Google Play? It’s an honest question. I assumed that the provider option I had in MicroG was exactly for that purpose, but I could be wrong. Next, a small rant. Bloody hell, I really do appreciate your politeness, but how is it that every damn article about privacy starts with threat modeling, but every discussion about privacy ends with “yeah but if your threat model does not require QubesOS you’re doing it wrong”? (I use Arch BTW)

Open ##495782