Note privacy implications of GrapheneOS proxy services

[Parish2555]

@marsha

There are a lot of reasons people wouldn’t want to trust GrapheneOS or Google.

Saying something like this, to me, is more then just pointing out that its a shift in trust. Especially because you list GrapheneOS and Google as examples for the same point, which makes it seems like you think they are equally untrustworthy.

[Encounter5729]

@Eireannach

if a product is open source you still can’t be sure that the source code available is the same as running code.

Yes, but even one instance where the code isn’t the same and the dev career ends overnight.

@Eireannach

I think all the OP is saying is that one still should be aware that using Graphene requires one to trust Graphene’s developers .

No

[jonah (Jonah Aragon)]

@Parish2555

Especially because you list GrapheneOS and Google as examples for the same point, which makes it seems like you think they are equally untrustworthy.

Or it was because they are the only two relevant examples in the situation lol

[Parish2555]

@jonah

Or it was because they are the only two relevant examples in the situation lol

I would pose the question then, in this context, when would shifting trust from Google to GrapheneOS be a riskier or equally as risky a move as the opposite?

[Lukas (Lukas Dutovas)]

@marsha

There are a lot of reasons people wouldn’t want to trust GrapheneOS or Google.

Then the only option is iOS.

If one is using any AOSP based OS, they have to trust Google, and if you’re using GrapheneOS, you still have to trust Google and GrapheneOS.

This topic is completely pointless, replacing these connections with GrapheneOS ones is a feature and not a bug. You also have the easy option to switch back to Google’s ones if you want that for some reason.