21–30 of 927 posts
Let me play out a scenario, imagine to use a Desktop Hardware like a complete built rig, you would need a specific OS like Windows 11 and you could not run Linux on it, just because it's a vendor lock-in. Why is this acceptable for phones but would not for the case above? I know a lot of people don't care, and that's ok, but we should root for an open choice for the users.
Earlier quoted context omitted.
I see zero trouble as long as it requires no additional identification, no additional payment, and no mandatory time limit for the sideloaded apps. That is, fine by me. I can wait for 24 hours once in a few years when I acquire a new mobile phone.
Why would you do all that to install an app in a device that you own? It's bollocks.
Look, I can't locally install a web extension I wrote on an open-source Firefox browser, because security. I have to install a Developer Edition, or get the extension reviewed and signed by Mozilla, for the very same reasons of thwarting scammers. Is this stifling, or is it making my browser not mine? Is anybody making a big deal out of that?
The world we inhabit is not always friendly. It has a ton of determined and sophisticated bad actors, and a lot of people with less technical savvy than you and me. We have to deal with that, instead of being cantankerous.
I don't care, I run Graphene, and my phone is definitely mine. Most Android apps just work, and the ones that don't are the kind of malware I am happy to do without.
But beyond whether the OS is good or not, "fuck you, I've got mine" is not only sad as a position in general, it is also a bad tactical choice, because over long enough timeframes you can't assure that you can keep yours if others are deprived.
Earlier quoted context omitted.
From TFA: Delve into System Settings, find Developer Options Tap the build number seven times to enable Developer Mode Dismiss scare screens about coercion Enter your PIN Restart the device Wait 24 hours Come back, dismiss more scare screens Pick "allow temporarily" (7 days) or "allow indefinitely" Confirm, again, that you understand "the risks" Nine steps. A mandatory 24-hour cooling-off period. For installing softw…
I see zero trouble as long as it requires no additional identification, no additional payment, and no mandatory time limit for the sideloaded apps. That is, fine by me. I can wait for 24 hours once in a few years when I acquire a new mobile phone.
The opt out is graphene os yeah?
Yes, but there are issues. You can’t use stuff like banking apps on a modified device and losing access to normal android devices would be a big blow to the momentum of the F-Droid community. GrapheneOS might not be a big enough community to sustain work on the projects delivered by F-Droid.
IME such apps are few and far between. The most trouble I ran into is play store refusing to show apps because they claim the app isn't compatible with the device, but that can be worked around with aurora store.
Earlier quoted context omitted.
Why would you do all that to install an app in a device that you own? It's bollocks.
Because grandmas all over the world are getting swindled by scam apps. Look, I can't locally install a web extension I wrote on an open-source Firefox browser, because security. I have to install a Developer Edition, or get the extension reviewed and signed by Mozilla, for the very same reasons of thwarting scammers. Is this stifling, or is it making my browser not mine? Is anybody making a big deal out of that? The…
I don't care, I run Graphene, and my phone is definitely mine. Most Android apps just work, and the ones that don't are the kind of malware I am happy to do without.
I have a pixel 10 pro and have tried no less than 5 times to get my apps to work on graphene, no luck. I'm no slouch either, I've developed for android for almost a decade. I'm not disagreeing with ya, just adding a comment so folks are aware that the "Graphene just works" crowd is sometimes a bit hyperbolic.
(idle interest; I use Graphene, but few apps, and everything worked so far)
The opt out is graphene os yeah?
Yes, but there are issues. You can’t use stuff like banking apps on a modified device and losing access to normal android devices would be a big blow to the momentum of the F-Droid community. GrapheneOS might not be a big enough community to sustain work on the projects delivered by F-Droid.
This is why I've stuck with Android for the past 15 years.