After the news cycle recently exploded with the announcement that Google would require every single Android app to be from a registered and verified developer, while killing third-party app stores …
But if Graphene chooses not to do this, they diverge from the Android project. Which will take more time to maintain the project which will ultimately lead to more developers burning out and dropping out of the project.
It doesn’t need to be affected, but most open source projects don’t have the resources to keep going against big companies when most of their users aren’t contributing.
GrapheneOS wasn’t going to be affected anyway and there’s nothing for the GrapheneOS developers to change. The developer verification thing will be done by proprietary Google apps. Those apps cannot get the necessary permissions to block app installs or disable apps.
They already diverge by having a network permission and a bunch of other differences, and not being allowed to use Google Pay because of those differences
That might be true, I don’t know much about GrapheneOS.
But I do know that users of open source projects expecting changes to come out of thin air, and filing bugs when they don’t, is hurting the volunteers behind open source projects.
So we should all make sure to volunteer some of our own time or money to keep the projects we love going, instead of just expecting them to fix the things we dislike.
The aosp has been in the process of being gutted, I surmise in preparation of these anti consumer measures, graphene os has its work cut out for it. I imagine that after the dust settles, consumers will have to pick between an immature Linux os or their personal preference of walled garden.
But if Graphene chooses not to do this, they diverge from the Android project. Which will take more time to maintain the project which will ultimately lead to more developers burning out and dropping out of the project.
It doesn’t need to be affected, but most open source projects don’t have the resources to keep going against big companies when most of their users aren’t contributing.
GrapheneOS wasn’t going to be affected anyway and there’s nothing for the GrapheneOS developers to change. The developer verification thing will be done by proprietary Google apps. Those apps cannot get the necessary permissions to block app installs or disable apps.
They already diverge by having a network permission and a bunch of other differences, and not being allowed to use Google Pay because of those differences
That might be true, I don’t know much about GrapheneOS. But I do know that users of open source projects expecting changes to come out of thin air, and filing bugs when they don’t, is hurting the volunteers behind open source projects. So we should all make sure to volunteer some of our own time or money to keep the projects we love going, instead of just expecting them to fix the things we dislike.
The aosp has been in the process of being gutted, I surmise in preparation of these anti consumer measures, graphene os has its work cut out for it. I imagine that after the dust settles, consumers will have to pick between an immature Linux os or their personal preference of walled garden.
I would guess that it’s probably not much by way of change — theoretically, maybe just a single line patch — to cause this check not to take place.
Theoretically it might be, but it’s another patch you’ll have to maintain
Graphene could sandbox the integrity check, just like they do with the Play Store.
It becomes an integrity check arms race. Graphene OS devs not keen on this idea, but they may not have a choice in the near future