▲ | Andromxda a day ago | ||||||||||||||||||||||||||||||||||
> you can still get identified and tracked even if you use a VPN Sure, but that requires additional data about the user, which the GrapheneOS update server doesn't get. Both the update client and the update server are open source, so you can verify any of what I'm saying. The server only sees the user's IP address, which device model they're requesting an update for, and which update channel (alpha/beta/stable) they are using. The HTTP headers, etc. for the request would be identical across any GrapheneOS device, as they use the exact same updater app. https://github.com/GrapheneOS/releases.grapheneos.org https://github.com/GrapheneOS/platform_packages_apps_Updater > First, he is under no obligation to spend hours learning how GOS updates That literally takes a few minutes to look up, it's all really well documented on the official website. https://grapheneos.org/faq#default-connections But yes, I do believe that he's obliged to do some research before putting out such absurd claims entirely based on speculation with no technical knowledge or understanding. | |||||||||||||||||||||||||||||||||||
▲ | bernoufakis a day ago | parent [-] | ||||||||||||||||||||||||||||||||||
> That literally takes a few minutes to look up, it's all really well documented on the official website. https://grapheneos.org/faq#default-connections Again, that is beyond the point. The developer going rogue (for arbitrary reason) and turning the code malicious is not impossible. > That literally takes a few minutes to look up, it's all really well documented on the official website. https://grapheneos.org/faq#default-connections All of you who keep commenting "But it's so easy, just look it up" are lacking consideration and empathy. Other people don't think like you, they don't have to think like you. Just the documentation you have linked has so many technical terms, someone not familiar with networking and system design will barely make any sense of it. It is a also a matter of trust. After the developer express their hostility multiple time, even if someone was willing to go through it, what if the documentation is not forth coming ? It is within the devs control after all. How does one even make sure that the software does what the documentation says it does ? etc... > But yes, I do believe that he's obliged to do some research before putting out such absurd claims entirely based on speculation with no technical knowledge or understanding. What "absurd" claim did he put out exactly ? His issue was never about the technical aspects of GOS. It was about the broken trust and the perception that using software from a hostile developer was a risk factor, hence his stopping using it (at least on his devices with sensitive info). | |||||||||||||||||||||||||||||||||||
|