Sideloading is fundamental to Android, and it's not going anywhere. As we said in our blog, our new developer identity requirements are designed to protect users and developers from bad actors, not to limit choice. We want to make sure that if you download an app from a
@ssamat It's a strange time to talk about Android protecting users. Android recently changed the security update system in a way which massively downgrades security and puts users at risk. Commercial exploit companies and governments can easily obtain access to broadly distributed
@GrapheneOS @ssamat Are you guys going to support additional phones other than Pixels?
@kryptosgraphein @ssamat Yes, once there are non-Pixel devices meeting our requirements (#future-devices). class="text-blue-500 hover:underline" target="_blank" rel="noopener noreferrer">https://grapheneos.org/faq#fut... Current non-Pixel devices allowing another OS lack the security features and driver/firmware updates. We're working with a major OEM towards their future devices meeting these requirements.
@GrapheneOS @ssamat Does this mean Daniel/GOS is officially changing its position from "you have to trust Google" and admit everyone they mocked for years was exactly correct? Thousands of people brought this concern to GOS since inception and it was always met with vitriol.
@ascetic_tweeter @ssamat The claims you're making about us are extraordinarily inaccurate. We've criticized Android, Linux and Pixels for where they have failings for years. We haven't mocked anyone. Personally targeting our founder with fabricated stories is very typical for people malicious towards us.
@GrapheneOS @ssamat Part of their deal with Israel?
@xphitakhon @ssamat No, and stuff like this is a distraction from our post that's going to help them ignore it.
@ssamat Our reply here was linked on Hacker News with an inaccurate title ("Delayed Security Patches for AOSP"). Security patch backports were pushed to AOSP on September 2nd for Android 13, 14 and 15 as expected. More information is available at https://x.com/GrapheneOS/statu... explaining the
@GrapheneOS @ssamat I'm glad I switched to GrapheneOS. I don't want to go back. I donate to the team every now and then. Freedom is non-negotiable.
@GrapheneOS @ssamat 🎯
@GrapheneOS @ssamat Appreciate all your work in this field!
@GrapheneOS @ssamat Is it a given that Android is going backwards from a security perspective ? Is it reasonable for the GrapheneOS community to continue to expect superior output from you guys ? Or have you been dealt a heavy blow ?
@GrapheneOS @ssamat One wonders whether Google's delays in patching AOSP might not be at the behest of the United States government.
@GrapheneOS @ssamat So in the worst case, Android 16 QPR1 won't be pushed to AOSP?
@GrapheneOS @ssamat This isn't looking good....
@GrapheneOS @ssamat Is hard forking AOSP something @GrapheneOS would entertain? Or are the potential hardware compatibility considerations too great?
@GrapheneOS @ssamat I sure as HELL don't believe a damned thing they claim. Why should I? Why should anyone.
@GrapheneOS @ssamat Grapheneos, your concerns are valid and deeply troubling. 🧩
@GrapheneOS @ssamat Maybe that's the point. So that commercial exploits and governments can gain access? And the mass user will be given minimal basic protection against common exploits, like the Chinese os
@GrapheneOS @ssamat @topjohnwu Do you have any information about this?
@GrapheneOS @ssamat @ssamat at least have the decency to reply to them.. They are widely recognised security focused OS after all
