And that’s exactly google intention. All that “security” bullshit is to justify this.
Without something like f-droid google hopes that someone like me who despises them will be forced to use play store.
And I’m sure many of us will bend. But as for me, I’d rather go back to dumb phones if Linux phones don’t work. And google board members can stick their security on a pineapple and stick it in their ass.
With a condom of course because i want them to be safe while being fucked, just like they wish for us.
So what app store should one move to, in that case?
None. Move out of Android. Their dick move is deeper than just fucking up alternative stores. It’s to make sure it’s not worthy for anyone to publish outside of play store.
For your safety, of course. Nothing more at all.
Let’s invest in Linux options.
Malicious actors will still succeed in registering their apps, so the whole thing is only good for control.
Google claims that the changes are being introduced to protect users from “bad actors spreading malware and scams,”
Google Store should be closed down too, because it spreads malware and scams too.
Nearly all malware comes from the play store, given that very few people get apps from elsewhere (percentage-wise).
I can’t imagine this to go through everywhere in the world. In example even Apple is forced to allow sideloading in Europe. So why would Android not be forced too, especially because it had it before and is even more widespread than iPhones. I also wonder how many people using an Android phone do actually install applications outside the Google Store? I mean besides pre-installed stores like for Amazon Store or Samsung Store. The sad reality is that most people don’t care or use sideloading at all. (Edit: Typo.)
This is different, by design. Sideloading and alternate app stores are still perfectly fine. It’s just that the developer has to give a bunch of personal into to Google in order for their app not to be rejected by the phone itself. Middleman doesn’t matter which is where most if the regulations are. Problem is that many open source apps don’t have a developer willing to spend the time and money or give up their privacy in order to publish an app they don’t make money on. So it’s designed to kill off FOSS apps.
As the F-Droid team signs the (not repoducibly built) apks with their own key, Google would have to allow the key of the F-Droid team then.
Yet, as Google currently does not permit apps in their PlayStore that aren’t in line with their business model, e.g. NewPipe, they would then force the F-Droid team to do the same.
They said they can’t do that in the article:
but at the same time, we cannot ‘take over’ the application identifiers for the open-source apps we distribute, as that would effectively seize exclusive distribution rights to those applications
They would need to modify the ID then.
OSMand, e.g. has different IDs in PlayStore and F-Droid (+vs.~suffix).Edit: It’s the names that are different, the IDs are the same.
Possibly, but I don’t see Google doing that either. It’s not about where the app comes from really. The thing they are going to restrict is the developer. A developer can not have their app installed on a certified phone, regardless of where the user got the app, if the developer is not registered.
So, since there are no regulations to allow a user to install apps from any chosen developer, only from any chosen app store, there likely will be no regulatory recourse like Apple is facing as mentioned by the OP.
My first point is, in other words: From Google’s pov, the F-Droid team is “the developer” who’s key and personal information Google would request to allow installing apks with their signature on Android devices.
