benchess

- It's not possible to set screen time restrictions for Safari.

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.

Heya, wanted to show off a project of mine to identify the scaling limits of a large Kubernetes deployment

The irony of posting this on GitHub which remains shamefully without IPv6

It’s mentioned

My kids like reading this over and over: Now & Ben: The Modern Inventions of Benjamin Franklin: https://a.co/d/jhm2SvM

Use a dns proxy and https://github.com/froggeric/DNS-blocklists/blob/main/NoAppl...

You may also need to disable Private Relay

They’re for sale on Mouser for $20625 each https://www.mouser.com/ProductDetail/BittWare/RS-GQ-GC1-0109...

At that price 568 chips would be $11.7M

This isn't running on one chip. It's running on 128, or two racks worth of their kit. https://news.ycombinator.com/item?id=38739106

This doesn't mean much without comparing $ or watts of GPU equivalents

If I understand correctly, Groq chips have 220MB SRAM and the next best level is DDR4? How many chips are needed to run Llama2-70B at those speeds?

The key constraint here is that the author has no access to persistent disks and can only use object storage for persistence. Otherwise Thanos would be extreme overkill for this number of metrics.

Single-node VictoriaMetrics can easily handle 1M metrics/sec

Hi, co-author here. Yes we are excited about the potential of this!

Hi, co-author here!

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.

Hi! Co-author here. We do keep the nodes running 24/7, so Kubernetes still provides the scheduling to decide which nodes are free or not at any given time. Generally starting a container on a pre-warmed node is still much much faster than booting a VM. Also, some of our servers are bare-metal.

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.

It's all pretty well covered in the Methodology section of the about page: https://takecongress.org/about.html

Utilize SNI and serve up a fake cert when someone scans you without a matching hostname. Censys is scraping you by IP, so it'll just see the fake cert.

You can do this in nginx by making the fake cert the first server block.

Not all bandwidth is created equal. Different providers can have widely different levels of performance. Higher-priced bandwidth _can_ also be better bandwidth.

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.

What an amazing story. Great to hear of people like Katherine!

So when you hit the limit you want AWS to stop your spending... how?

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?

Also Stratos https://stratoscard.com/

"No planned downtime: Local SSD data will not be lost when Google does datacenter maintenance."

Only unplanned downtime then :)

Live migration maybe adds another '9' to reliability, but customers still need to plan for failure.

It's both a product and a platform. plus.google.com and its "What's New?"-style newsfeed is a tangible product.

The news that Google+ integration is no longer required for other Google products means the platform is deprioritized.