Google will require developer verification to install Android apps, including sideloading

That’s a violation of a certain ArceusLandic law there (What that company is doing of course). So clearly these companies & governments are getting more power hungry. They want everything about us. Be we will resist harder & harder, teaching them a stern lesson in respecting privacy and freedom of rights & free speech.

1 Like

How about maximum resiliency. Make it Linux based and run Android using waydroid. That means Google won’t be able to take it all the way down or break it somehow.

Any link where we could find out more about this Arceus AOS?

To answer the first thing: It’s theoretically possible, but then it would be Arceus LOS (Arceus Linux Operating System) with Android compatibility, so basically it would be a privacy oriented Windows 11. Which honestly isn’t bad.

For the second thing: Unfortunately, I only made this concept very recently, since the Arceus 2600 is the first concept I made, and the Arceus AOS came well after that.

Every day, the situation only gets worse as Google continues to crack down on FOSS. But we must also remember that every system can be defeated if people are willing to look into how things work and how different methods have either worked or failed in the past.

3 Likes

You’re correct, we can defeat Google’s systems, like their Age Verification or Developer Verification, since they have to store settings data on a server, I think we may be able to break their systems and negate their Age Verification & Developer Verification simultaneously, but we need to know which servers such settings data would be on…

1 Like

Funny and irritating thing,
I actually wanted to argue on behalf of Google,
that they are doing the best they can to keep their tech open source
while running a hugely successful business
among the pressure of deadlines, board of directors, governments and other power groups.

Wanted to argue, that they’ve actually did a lot of work to keep Google Mobile Services (GMS) users’ digital lives safe.

Believed,
that Google provided developmental, managerial and infrastructural resources for AOSP
- which is a bedrock upon which further Android systems are built,
like One UI, LineageOS, AXP.OS, etc.
- for no explicit monetary gain.

And as I conducted a research for a somewhat thorough post,
I’d just learned, that there’s actually a licensing fee for manufacturers who are going install GMS on the devices they produce.

I felt, I could not justify Google’s Developer Registration Decree no more.

3 Likes

Which led to liquidation of KMS. :pensive_face: Administrators called in at hardware firm KMS after row with Argos | Software | The Guardian

1 Like

Google is doing it for monetary gain, we all know the jist of these corporations: Maximize Profit, Minimize Spending. Google literally sells any data on individuals to other corporations to serve ads, and that there sparks the problem, since your data is literally everywhere, it would essentially be a huge risk to the people, because just one hack could jeopardize everybody on Earth. Case closed.

What a sinister Argos smile.

Whatever the backdrop of the story and behind-the-scenes power plays,
the story looks obnoxious. :frowning_face_with_open_mouth:

Yeah, cyberpunk espionage looks cool in books, video games and movies.
Yet, in real life, monopolized data brokering is annoying at best.

1 Like

Good thing, there’s a push back campaign going on right now.

1 Like

Annoying, but also dangerous because hackers would have additional options to hack to get the same data.

It’s still a extremely privacy invasive component that is privileged in a very unsafe way on most devices. Granted depending on the device it may actually need some of those privileges like to apply updates. But then why not just make a updater that actually respects the user to run in the background? But it’s not entirely surprising given that most of Google’s apps are unnecessarily privileged on most Android devices

No matter the good it does it’s implementation is extremely problematic and honestly deserves all the scrutiny it gets.

But I can’t deny there is a lot of truth to what you are saying. I mean one of the biggest things right now is RCS even though that should have been a open standard (Thanks Google…) But the fact of the matter is right now it isn’t so that added protection is cause of GMS.

1 Like

But, users can secure their devices without Google even getting involved at all.

2 Likes

The EPIC resolution in my eyes is a gimmick tbvh. The way things are going, makes no sense to me.

1 Like

look into how things work

Cryptography, key pair (public key & private key), signature, certificate, PKI, CA. I’m studying for an exam, so I can explain a lot.

how different methods have either worked or failed in the past

An attempt to fight against some form of centralization will usually fail, as it is against the trend of historical and technological evolvement. Ironically, the easiest way to defeat centralization is to replace it with another form of centralization. Only a walled state can defeat a walled garden. We cannot rewind the time or pretend that asymmetric cryptography is not yet invented; once it is invented, it will be used. We cannot stop the time or prevent certain use of a technology (except by regulation, which is a form of centralization). The world is changing, from a better era to a worse one; no one or no company can fight this trend. What we can do in this moment isn’t asking why there would be control, but who would have the control and hold the ultimate key that will be used to sign every important certificate in the next era.

Also, hacking isn’t the way. Google’s servers won’t be easier to crack than the devices and operating systems they produce. If you expose their singing key, they can likely change it (Kerckhoffs"s law), and the freedom is just a while; if their servers no longer function, a likely result is that no one can install any app on any device (Fail-security).

1 Like

Two questions about Google’s proposed shitifcation of Android:

  1. If you have F-Droid already installed, do they remove it?

  2. Is there some developer mode where you can bypass Google restrictions and install F-Droid anyway? If so, is there a way to streamline it to make F-Droid installation ease-o-matic?

they did not say yet

maybe: Neil Brown: "Google is starting to retreat on its "developer g…" - mastodon.neilzone.co.uk

We don’t know yet

Hmm…Maybe as a Failsafe we should find a way to pre-install F-Droid on all devices. That way the access will always be there, but how can we achieve that? We would need to access the core aspects of the Android device in order to set F-Droid as a System App…

not really, surely there’s a company that can make that happen…