Technology

with a 24 hour delay guarunteed to punish anyone who wants to have their device their way.

the win in this is that many people realise how locked google has made android and how blatantly and arbitrarily google exerts their control over it. hopefully that will be input to some consumer decision (when sailfish becomes an alternative) and a tiny bit more people will consider their choice when getting a new phone. and maybe it also helps some regulation to be agreed (in europe, obviously).

I want an extra day added to the warranty of any device I purchase, as it will be useless during that time

Software freedom or demise. While Google is capable of imposing anything then Android is already dead to me.

If the process doesn't include any phone home stuff, and is just a one-time cool off period to prevent scammers, this is acceptable to me. That should be enough to get potential victims to self-question, ask more knowledgeable people of what's going on to avoid being unknowingly hacked, without being naggy every time for users that want to do what they want.

Making a software "foolproof" will probably invent a bigger better fool, hoping for some sort of free crypto app jumping through these hoops, but this should weed out most of the basic scams.

You win by disabling software updates at Android 15.

Then make the wait period a week, a month. Have this privilege expire every so often etc.

Try to pull warranty shenanigans if you ever went through the process.

What do they mean reauthenticate after 24h? I can't authenticate as I don't have a Google account. Although I do unfortunately have Google play installed, my phones can't have it removed.

Nah, American companies cannot be relied upon by definition. Even if the people running one are fine (and many are), they are still based in what is essentially a pro-crime, pro-corruption jurisdiction.

I think the 24 hour wait is at least a sensible alternative. Anybody who's going to be seriously installing apps on their devices like this is probably going to be using Lineage OS or Graphene OS or /e/OS or something like that anyway. And in that case, they will be using AOSP and not be subject to this because they're not running a Google certified device.

While I'm not particularly happy about this change, I think it could be way worse.

Something tells me that Google drastically underestimated the amount of pushback they were going to get when they announced this. I mean, very drastically underestimated.

Its seems fine, other than the whole "coaching" thing. Like, nobody knows how to do this today, so someone will have to "coach" them through it, even if it's Google themselves.

But I would wait and see exactly how it's implemented before calling off the resistance. And I wouldn't call it a "win", that would be then backing down entirely back to what they were already doing.

at best this is not losing at this very moment