The "advanced flow" will be available before verification enforcement begins later this year.
See full article...
See full article...
You're absolutely right, I have also enjoyed a Pixel with GrapheneOS for a long time.I've been running GrapheneOS on my Pixel for six months now with zero issues. Highly recommend to those with compatible devices.
Google can fuck right off with their enshittified bullshit disguised as "safety".
ETA: When I pay for a computer it needs to do what I tell it to do, when I tell it to. Nothing more, nothing less. For those of you who read this that work for these companies....for the love of fucking christ, stop being evil.
I think one of the options that will fulfill your wish is Fairphone with MurenaOS (/e/OS)I am really hoping the fall of American tech abroad will mean that in the next 5 years we have a real (open source) alternative to platforms owned by either Google or Apple with broad app support. I don't care if it's a deGoogled Android fork (easier as a third common app deployment target), a mainstream Linux phone, or something else.
It really is crazy we let two companies from a single nation dictate the smart phone experience for 8 billion-ish people.I am really hoping the fall of American tech abroad will mean that in the next 5 years we have a real (open source) alternative to platforms owned by either Google or Apple with broad app support. I don't care if it's a deGoogled Android fork (easier as a third common app deployment target), a mainstream Linux phone, or something else.
It really is crazy we let two companies from a single nation dictate the smart phone experience for 8 billion-ish people.
Would a scammer pushing a non-verified bad app really do so by trying to publish it on f-droid?Yours is understatement. The Play Store is a hot mess, F-Droid is safer in totality, many thanks to the developer community, and its not so much a bit funny as quite hilarious albeit the laughter is the laughter of irony.
The good news is that Linux phones, while still alpha quality, are wayyyyy beyond where they were about 3 years ago.
You forgot the other upside. Every developer on F-Droid now owes Google $25 for absolutely nothing in return.So the downside is that I have to wait 24 hours before I can install F-Droid on my next phone.
The upside is that scammers cannot trick clueless users to install malware as easy.
I can live with this.
Your bully isn't a nice guy just because he lets you pay him $25 to stop punching you in the face.Yeah, I'm in your camp here as well. This whole process actually seems somewhat reasonable. I know it's fashionable here to consider Google to be The Great Satan, but it seems at least possible that they're actually trying to combat bad actors. Sure there's malware in the Play Store, but they are trying to manage it. There's also bad stuff in Apple's App Store, and none of the stuff in the official stores is as bad as the apps that unwary users get tricked into installing by scammers.
I think, overall, the Ars commentariat is probably too hard on Google. They've built a relatively open ecosystem. OSes like GrapheneOS couldn't exist without AOSP, and even the devs on that product appear pretty frequently to get exhausted by all of the anti-Google vitriol. Android today really is a mess of malware and scamware, and it's bad for Google, and Google's brand, and their users.
Sure, Google is an advertising company, but they actually don't sell user data; they just use that data to place ads. Apple collects the same exact data in the same exact way; they just use it internally and don't allow marketers to use it for ads. Also, Apple supports a tyrannical regime in China and doesn't allow any user freedom at all, while Google left China out of principle and publishes source code for one of the most complex pieces of software in existence.
Yeah, I'd love it if Google didn't do any surveillance and somehow funded AOSP with magic money, but that's not a particularly reasonable request. They could be better, but in this case, I'm willing to give them some benefit of the doubt. 24 hours one time per phone is just not a big deal.
You mean like how the article mentions there's an "allow indefinitely" option?But allowing us to turn off the 24 hour wait after the first time permanently would be so much better.
They probably are saying that because open source mobile software stacks using Linux actually exist.We are definitely in need of a third option but is a linux phone really a good option? that's what android is, a phone OS built on top of the linux kernel.
There's a huge amount of work involved to keep android up to date with the mainline kernel. A lot of regressions to deal with etc. Then of course phone manufacturers needing to rebase their phone on the new kernels too. Maintaining LTS releases is a huge amount of work too.
Why is all that needed? There's so much in the linux kernel that is unnecessary. So many security vulnerabilities as a result. All the work involved due to being downstream.
If we're going to have a serious third option it should be using a purpose built microkernel. That's what Huawei have done with HarmonyOS NEXT, their android replacement.
Just because linux exists doesn't mean that's the right way to go.
I kind of think this article should've included information about why they are actually doing this: the Epic lawsuit rulings. Where Apple got off lighter than Play Store because of the open garden.
And this is precisely how massive corporations get you to give up your rights to them. You can live with this seemingly innocuous change, but they've just shifted the window in their favor. The next shift will no doubt also feel "acceptable".So the downside is that I have to wait 24 hours before I can install F-Droid on my next phone.
The upside is that scammers cannot trick clueless users to install malware as easy.
I can live with this.
Unless I've missed something, waiting 24 hours is legitimately the only major change here. That's a grain of sand's worth of movement on the alleged slippery slope.And this is precisely how massive corporations get you to give up your rights to them. You can live with this seemingly innocuous change, but they've just shifted the window in their favor. The next shift will no doubt also feel "acceptable".
Imagine having to wait 24 hours before installing whatever software you wanted on Windows or macOS. It's an absurd suggestion.Unless I've missed something, waiting 24 hours is legitimately the only major change here. That's a grain of sand's worth of movement on the alleged slippery slope.
I think you're missing that the 24 hours thing can be a once and done thing, if you choose it to be so.Imagine having to wait 24 hours before installing whatever software you wanted on Windows or macOS. It's an absurd suggestion.
And, like I said earlier, this is a requirement that can be very easily ratcheted to become increasingly burdensome over time. A slippery slope is not inherently a logical fallacy unlike the alleged security argument being used to push this corporate control over other people's computing devices.
Nope. I fully understand this just fine. I own the device. It is mine. The 24 hour waiting period, even once, is wholly unacceptable.I think you're missing that the 24 hours thing can be a once and done thing, if you choose it to be so.
I'm sorry, but this is an exceptionally lame cop out. You personally need a week to setup an OS so the entirely artificial 24 hour waiting period (like I'm buying a gun ffs) is therefore reasonable to foist on literally everybody? You cannot possibly be serious. "I drag my feet when setting up a new computer so therefore it's okay to surrender my and everybody else's sovereignty to a massive corporate entity." Helluva an argument you got there.And I don't have to "Imagine having to wait 24 hours before installing whatever software you wanted on Windows or macOS." or Linux, or iOS for that matter. Daily life enforces that scenario whenever I need to set up a new device.
If it takes me less than a week to have a new device fully up and running the way I'd like to daily drive it, then it's been a very quiet week. It's a time consuming and tedious task, the sort of thing you procrastinate doing cause it's so boring even if you did have nothing to do for 12 hours.
Adding a 24 hour hurdle introduces a very marginal change to the order of installation and setup.
Hardly. The alternatives was to continue using Symbian with crappy mobile apps, because it’s clear we were never going to see the level of innovation needed to make modern smartphone ecosystems happen anywhere else.It really is crazy we let two companies from a single nation dictate the smart phone experience for 8 billion-ish people.
Is that confirmed? I didn't see that in Google's article, and the "developer mode" page says that all changed settings will be reverted when disabling it again.You only have to select the “indefinitely” option once on a phone, and you can turn dev options off again afterward.
You need some sort of a computer to write Android apps too, don't you?
What if I only have the Chicago Sun-Times? Pesky cat always shows up with it too.It's obviously smarter than that.
You need to upload a photo of yourself holding up a copy of tomorrow's New York Times.
If it's social engineering, they'll just be instructed to download stuff from the Play Store like Team Viewer anyway, so this shit is pointless.I see that I am in the minority with this opinion, but I think the 24-hour cooldown is a really good compromise to help prevent coercion and, more likely, someone with temporary unauthorized access. And for the power user who needs to sideload apps all the time, it doesn't seem too onerous to wait 24-hours once when you get the phone and set it to indefinitely allow.
The $25 fee and other hurdles for developers seems like the much bigger issue here.
No. That means unverified installs are allowed indefinitely. I want to be able to toggle that on and off without waiting 24 hours after the first 24 hour wait.You mean like how the article mentions there's an "allow indefinitely" option?
I think this is a reasonable take. I am not at all happy about these restrictions, but I'm more mad at the scammers who make it necessary to put up the roadblocks to prevent non-technical users from being marked than I am at Google for making it harder for people to get scammed.I assume this is your typical public/private key situation where Google gets the public key so they can verify the apps are signed by the dev private key. They can't sign something as the dev just verify the packages are from a particular dev who has been verified.
I don't think the $25 for verifying is that bad. It's a one time thing for an account as far as I can tell. That's pretty minimal and then you can presumably release as many apps as you want with any updates you want at any time. You don't want to make it completely free because people abuse the verified accounts and treat them as disposable. At least if you've got a minor fee there is some cost and you can do things like looking for someone verifying dozens or hundreds of accounts with the same payment info to try to prevent abuse.
I also think the 24 hours thing is fine. Your average user is never going to go into this in the first place. If you know you want to be able to side load things just go in and do this when you first setup the phone and set it to indefinite. You've now opened it up to side load as much as you want with out any delays. You've got your behavior that you want. I don't have a problem with the assumption that your typical person suddenly wanting to sideload something is probably being scammed and a 24 hour road block is probably a good thing.
Big if true. I tried finding other reports of this online to confirm, but instead found that they've been removing recovery-menu options, including ADB sideloading.So on my Samsung S24, they've already removed even the ability to enable Unverified Sources under Dev options, so unless they bring that option back, I won't even be able to follow even the basic first part of the instructions. It's a standard Samsung phone, so I'm concerned that since Google is implementing the restrictions, the function to regain the function won't be rolled out equally to locked OEM mobiles.
My S24 has been without the feature since the last patch, and I've been suffering a fair bit without it.
Also they may do the same shit they do on Google Play, where they will close your dev account for inactivity, and the only option is to create a new one and pay again. Not publishing anything for a year or two is not a sin.One time fees never stay that way.
And this is yet another step Google is taking in the long road to coerce people into stopping modifying their phones from surveillance capitalism stock. It has been going this way for years. Arguably since Samsung debuted Knox and corporate America thought that Knox was a great idea.
"At Google, we pride ourselves on allowing only authorised malware on our platforms ..."Avoid unauthorized malware on your phone while Google harvests everything you do and create to train their next shitty LLM.
well Google should have been broken up years ago - but that's why they formed "Alphabet".I would bet $10,000 that Google won't verify the developer of any app that gets around ads in YouTube. Why take $25 from one dev when they can take $23/month/user indefinitely?
This isn't to combat malware. It's to reduce the simplicity of installing apps that reduce income for Google. They won't say that though.
I have an old Pixel 6 Pro from a previous job that I've run both /e/OS (community build) and Graphene (officially supported) on to test. Subjectively I don't feel either is mainstream ready yet, especially with app support which is going to require some ecosystem building. They both have their solutions for running Google Play Store apps (after you retrieve the Google Play Store itself) but it's still a compromised experience because of the way apps expect official Android.I think one of the options that will fulfill your wish is Fairphone with MurenaOS (/e/OS)