

If I can’t rm -rf my root directory, then I’m not happy
If I can’t rm -rf my root directory, then I’m not happy
security risk
All those rooted concerns are true for desktop Linux / MacOS, and they still ship with sudo. If I can’t rm -rf the root partition then its not really my device.
The bootloader wall of shame is nice.
Yes, absolutely.
Phones that don’t support Google play services (AKA any hardcore privacy phone) will not be directly effected by Google restricting sideloading. The restriction is only for phones that use the Google suite. (source: https://9to5google.com/2025/08/25/android-apps-developer-verification/ “This requirement applies to ‘certified Android devices’ that have Play Protect and are preloaded with Google apps.”) Graphene OS isn’t going anywhere, AOSP is open source, even if Google tried to make that change in the OS, the community would hard-fork AOSP instantly and continue like nothing ever happened.
Realistically this is going to squeeze people “in the middle” towards fully-google controlled Android (one exteme) and towards fully-de-googled Android (the other extreme). Its just elminating the middle. Which is bad for people trying to gradually de-google their life, but not as dire as it might seem.
On the bright side, this is an opportunity for play-services spoofing to become commonplace and easy, and could cause more apps to avoid google play services. The EU also has a shot at forcing google to allow sideloading, since they’ve recently been forcing Apple to move in that direction.
So, while not a bright future, its far from hopeless for privacy respecting Android phones.
Good guess about the federating problem. Thats a good reminder for me to change instances (was on lemm.ee before it died, .world was my backup).
OTA, while a fair point, again sounds to me like a technical problem, not a fundamental design problem. E.g. disable the partion hash check so OTA can be installed in a timely way.