It cracks me up that the toggle for this advises you that it will cause your battery to die faster

Displaying seconds on macOS also causes higher CPU usage for WindowServer.

I'd think it'd be useful to opt-in to a 24-hr app installation blackout for scenarios like this.

But also, Google would definitely give 5-eyes a tool to bypass this for whatever they wanted to do to your phone.

Good point.

It'll be interesting to see how the timing is enforced. Can you just set up your own NTP server to fool your phone into thinking it's really the future (and not just you adjusting your phone's clock manually). Will Google run a clock that you have to get a timestamp from (would it be easy to setup your own MITM proxy to get around this?). If the time somehow jumped backwards, would you lose the ability to install apps? Can google remotely disable this after it's already enabled (I think yes)?

They're treating users like toddlers. Having to wait 24 hours to use my phone how I want to?

Assuming she pays taxes on the house, who cares if she lives there?

A case like this is still theoretically winnable, different courts have different opinions, and higher level courts have yet to weigh in

My new ToS I sent them allows me to appoint anyone (including my self) as the arbiter.

Have had issues w/ doing k8s over residential wan once I had enough hosts in my cluster

(though they were halfway across the US from each other, and not town)

So far everything is under 15ms apart, but it is a small number of nodes so far. Did you mostly have trouble with etcd?

Yeah, etcd was the main culprit, but latency was 150-300ms in my case. At 3 nodes, it was relatively stable (had an issue every week or so that lasted < 5 min), but at 4 the camel's back broke.

Lenovo (and their subsidiary Motorola) seem to be on a consumer friendliness streak