Eugen Rochko
AdventureTense@Gargron Even the term "Side loading", makes it sound non-standard and risky. Which of course, it doesnt have to be.
Joe W@adventure_tense @Gargron My best friend migrated his parents to Linux (20 y ago). The separation of admin and user accounts actually worked, software did not assume you were admin all the time, and he could let his parents only install software from trusted repositories. There is absolutely a case to be made for locking down the system. Don't forget, this is a pretty technically minded echo chamber we are in, what works for us is bad for others.
But I agree: It should be possible to do stuff!
But I agree: It should be possible to do stuff!
tranquil_cassowary@drchaos @adventure_tense @Gargron You can do it like Apple does for MacOS with notarization. Users can bypass it by going through several warning screens.
Kevin Karhan 
@tranquil_cassowary @drchaos @adventure_tense @Gargron #Ansroid does the same, demanding PIN & Confirmation to allow any "unverified" [not signed by Google] App to be installed.
@kkarhan @tranquil_cassowary @adventure_tense @Gargron Have you seen the plans? It will be very difficult for F-Droid etc to continue...
@drchaos @tranquil_cassowary @adventure_tense @Gargron I kniw and it pisses me.off as well!
Being greedy assholes wanting to monopolize shit is NOT a legitimate reason.
@drchaos @kkarhan @adventure_tense @Gargron
We don't know that yet. First of all, I don't think it's detailed yet whether Google will block developers from being verified based on terms that have nothing to do with the identification being real/accurate (e.g. no ad-blocking YouTube front-ends because it violates non-security related terms). A large amount of apps will be able to get verified probably because they won't violate any terms Google enforces, whatever those will end up being. Second of all, it won't apply to non-certified OSes. Whether it's viable for most of the apps on F-Droid to continue development if they would only be accessible on non-certified OSes remains to be seen. I don't know if there is any data about what percentage of F-Droid apps and FOSS apps in general gets consumed by people running alternative non-licensed OSes compared to licensed OSes developed by the Android OEMs.
We don't know that yet. First of all, I don't think it's detailed yet whether Google will block developers from being verified based on terms that have nothing to do with the identification being real/accurate (e.g. no ad-blocking YouTube front-ends because it violates non-security related terms). A large amount of apps will be able to get verified probably because they won't violate any terms Google enforces, whatever those will end up being. Second of all, it won't apply to non-certified OSes. Whether it's viable for most of the apps on F-Droid to continue development if they would only be accessible on non-certified OSes remains to be seen. I don't know if there is any data about what percentage of F-Droid apps and FOSS apps in general gets consumed by people running alternative non-licensed OSes compared to licensed OSes developed by the Android OEMs.
@kkarhan @drchaos @adventure_tense @Gargron
I only know how it works on GrapheneOS, currently.
It doesn't ask credentials for me upon install. It just wants me to allow alternative app stores or the Files app (for downloaded APK files) as an installation source for "unknown apps". It also asks that for the Play Store, given that that is a third-party optional app on GrapheneOS.
The "install unknown apps from source" permission doesn't have anything to do with who signed the app, just seems to have to do with the fact that it's not a bundled/default app installer like GrapheneOS App Store is on GrapheneOS.
I only know how it works on GrapheneOS, currently.
It doesn't ask credentials for me upon install. It just wants me to allow alternative app stores or the Files app (for downloaded APK files) as an installation source for "unknown apps". It also asks that for the Play Store, given that that is a third-party optional app on GrapheneOS.
The "install unknown apps from source" permission doesn't have anything to do with who signed the app, just seems to have to do with the fact that it's not a bundled/default app installer like GrapheneOS App Store is on GrapheneOS.