benchess
I thought this too. I discovered it actually is possible though, just doesn't appear in the list. Go "Screen Time" -> "App Limits" -> "Add Limit". In the "Choose Apps" dialog, you won't see Safari in the list. But you can type "Safari" in the search bar and it'll appear.
But I agree with the overall sentiment on this thread. iOS Parental Controls aren't where they need to be.
You may also need to disable Private Relay
At that price 568 chips would be $11.7M
This doesn't mean much without comparing $ or watts of GPU equivalents
Single-node VictoriaMetrics can easily handle 1M metrics/sec
We use a pretty standard tech stack of PyTorch + NCCL + MPI. We've used both OpenMPI and MPICH to varying degrees.
Kubeflow is interesting, but it solves a slightly different problem of scheduling/coordinating ML workflows on top of Kube. It doesn't get involved with how an ML job communicates within itself cross-node.
EDIT: Also don't discount the rest of the Kubernetes ecosystem. It's more than just a scheduler. It provides configuration, secrets management, healthchecks, self-healing, service discovery, ACLs... there are absolutely other ways to solve each of these things. But when starting from scratch there's a wide field of additional questions to answer, problems to solve.
You can do this in nginx by making the fake cert the first server block.
Cloud providers haven't done a great job of explaining this so far, but Google Cloud's Network Service Tiers product is a good attempt at why they charge more for bandwidth, and how you can get it for cheaper: https://cloud.google.com/network-tiers/
That said, cheap (and presumably slower) bandwidth may be the right target for B2, given that it's customers are probably using it for backups and private storage rather than, say, serving a website serving photos to millions of visitors from around the globe.
So comparing AWS or Google transfer costs directly to B2 isn't necessarily a fair comparison, depending on your needs.
You're spending $/hr on compute, so terminate your instances. Plus your EBS volumes, so delete your drives. Plus... S3? So delete all your data?
Only unplanned downtime then :)
Live migration maybe adds another '9' to reliability, but customers still need to plan for failure.
The news that Google+ integration is no longer required for other Google products means the platform is deprioritized.