The amount of people this makes angry is so minuscule that it probably wouldn’t even pass one of those theatrical “sign this petition to get the government to discuss it” thingy. Mind you, the only reason the whole side-loading court cases were going forward is because a giganormous company (Epic) wanted to make more money instead of paying the Google/Apple tax. Not because some people were angry.
This is political fantasy. There is no mechanism for "the people" to force anyone to roll this back. They can vote for the candidate owned by google, or the candidate owned by google. If they want to find another candidate, they'll have to use google to find one.
But often people try to project their opinions onto "the people" and predict they will rise up, and there's probably 100 predictions in comment sections that are completely spurious to every one that actually happens
So I'm not sure, but if I had to guess this one is a rare case where there may be real prospect of backlash.
I'd be interested in further reading on Google's outreach to big banks and major finance CO's ( or others) pushing for device attestation if you have any further reading.
https://sfconservancy.org/copyleft-compliance/vizio.html https://sfconservancy.org/blog/2021/mar/25/install-gplv2/ https://sfconservancy.org/blog/2021/jul/23/tivoization-and-t... https://events19.linuxfoundation.org/wp-content/uploads/2017...
But the Linux kernel is GPLv2, and only v2. For better or worse, locking down the bootloader is (probably) pernitted with the Linux kernel.
Having heard so much about anti-Tivoization when the GPLv3 was being drafted, and the discussions about it on linux-kernel when Linus decided the kernel will remain GPLv2-only, I was left with the impression that the GPLv2 only required the provision of source code, build scripts, etc. but not the ability to reinstall a new version. [1] makes a pretty good case that the ability to reinstall is also required GPLv2, and I'm heartened that's how Tivo saw it too.
[1] https://sfconservancy.org/blog/2021/jul/23/tivoization-and-t...
Right now, it seems to be fairphone or pixel, or old phones which are not easy to obtain. Samsung have announced they will lock their phones, and how long before google locks pixels?
This makes me quite angry, but I guarantee more than 90% of Android users will not be bothered too much about this. Many of them will actually like it, and most of those who don't will just shrug and go on with their day.
The weirdest thing to me is that those people who actually care about this are most likely the ones capable of implementing this shit: developers. Us. Who else but developers (OK, and maybe their enlightened spouses) cares about this? We are digging our own graves, basically.
So, Google devels: refuse this. And tell your willing colleague that they are not welcome at your birthday party if they do it.
I don't think that's it. The desktop OS situation has historically be similar with 2 major large players and a bunch of insignificant ones.
This comes down to user expectation.
There are two OS platforms for desktop/laptop usage: MacOS Windows
These both contain ways to run arbitrary compiled code from an arbitrary source -- like a computer should. Losing this feature of our smartphones should have everyone concerned.
And they're both working towards taking that away.
For now we have Linux as a 3rd option, but that only exists so long as there's hardware available that'll let you run it. Can easily imagine a near-future where you can only get 'Windows hardware' or 'Apple hardware' and nothing modern that'll boot a 3rd-party OS.
For precedent, Microsoft locked down their own ARM hardware to Windows.
It isn't possible to ban encryption, so the governments have to chip away at security and privacy using these techniques.
From: https://developer.android.com/developer-verification
"You may also need to upload official government ID."
This won't end well for Google or the governments involved when the people get so angry that they are forced to roll this back. Switch to an alternative phone OS.