This is a most excellent place for technology news and articles.
Since Google’s goal is to improve security
This is an obvious lie.
They never specified who’s security…
Their revenue probably felt very threatened.
Whose*
Who's = who + is
Whose = an indication of possession
I will always remember this grammar rule thanks to the show "Whose Line Is It Anyway?" because I would see that title every morning before school.
Call sideloading what it is, installing apps.
I know, I know. People don't understand how they've already conceded the war with language.
Me: Like...Yeah, I'm just going to "jailbreak" the small computer I bought to... run a program.
The public unironically: Oh man, I hope you don't get arrested.
Found the Rossman subrsciber. 📎
Like "Jaywalking", suddenly, walking is no longer the norm, but the car is preferred. The victims are seen as perpetrators.
It is, because it's actually the term that defines the process of transferring files not from an external networked device - downloading - or to an external networked device - uploading - but between two local devices - sideloading.
It's over two decades old, you downloaded an mp3 from kazaa, and then sideloaded it to your player.
For android apps, I believe the term originates from the method of using ADB to directly write the app to the phone memory, the command of which is "adb sideload filename"
And companies ofted do it. Thay recoined jaywalking to put the blaim of the accidents to pedestrians and take away the road from them. They change what littering means in attrmpt to delute the responsibility for polution... We are better than that this time, right?
I'm not sure why google is over engineering this, proper mainline distros have this solved since forever. Let the community setup trusted repos with gpg keys, then let me trust the repos. If Fdroid trusts the package and I trust Fdroid, who should care?
Because it was never actually about security to begin with. That's obviously BS. Google just wants control.
Probably because they want to target software that cracks theirs to avoid ads, like ReVanced.
Ding ding ding ding ding. It's so obvious, it's because Google wants to be in control and block apps it would rather not exist. Newpipe, FreeTube, Revanced and the like.
Since Google’s goal is to improve security
Is it though? Really?
The security of their bank balance.
This is actually worse than integration in Play Protect which can be disabled very easily. Now you can only install unsigned apps via ADB which means just developers can do it.
And very annoying too since some government apps don't like it when you have developer mode on.
Not only government. I can't see my daughter's insulin pump status if I don't disable developer mode.
Or anyone with a computer who installs ADB. You don't have to be a developer.
Nah you can't realistically distribute your app with adb requirement. No one will bother to go through such friction.
Leaving ADB open to unverified apps is more than I was expecting. ADB is reasonably straightforward to use even without actually being an Android developer.
There was never any way they'd integrate it to play protect and still allow play protect to be disabled. I prefer this to being required to use play protect personally, though the services do seem somewhat redundant. Presumably the whole point of doing this is to create an Apple style walled garden (which is of course very profitable). Google likely doesn't want to fully lock it down and risk legal trouble, they just need to make it difficult enough that the masses don't bother installing unapproved apps that may not act in Google's interests.
I still hope the EU takes legal action against this anyway.
I don't think this adds anything tbh as peoppe with adb would always be able to bypass this. The issue is that this kills distribution and thats exactly what Google wants - have full competitive control. Once they don't like your app they'll block your account and what do you do with your customer base? Give them adb install instructions? That's basically a death sentence for any app.
tl;dr you can still "sideload" via adb.
This is so incredibly inconvenient as to be meaningless.
It's not completely meaningless because if it's truly the only option I'm going to be using it until I eventually replace my current phone with one with an unlocked bootloader.
they always do this to gaslight us into accepting things we would not. when blocking installs from outside gplay is a possibility, further restricting it is a relief, not the outrage it should still be.
that or they got a feel for it and decided to settle with less restriction. for now.
the permanent solution as always is deposing them from this position of enormous power and monopoly. easy said.
So a lot of speculation and we don't know much except 2 paragraphs in the FAQ... I'd like to mention though, they've recently stripped the Pixel devices of their status as developer devices and now push for their emulator for development. Once they follow that kind of logic, there isn't really a reason to keep ADB working as is, at least not on real devices.
If Google wanted to add developer verification without being evil, it could use SSL certificates connected to domain names. I think the whole concept is ill-conceived, though I'll admit to a modest bias against protecting people from themselves.
We hope that Google keeps its word and preserves ADB installation
lol, adb is the first loophole that will be closed.
