Gotta love the word 'sanction'. It is it's own antonym!
"The committee sanctioned the new policy." (approved it)
"The committee sanctioned the rogue nation." (penalized it)
> Cloudflare, along with a majority of the world's leading publishers and AI companies, is changing the default to block AI crawlers unless they pay creators for their content.
It really seems that they did _not_ change the default, since this feature is in private beta.
I switched an agent from Sonnet V2 to o3-mini (default medium mode) and got strangely poor results: only calling 1 tool at a time despite being asked to call multiple, not actually doing any work, and reporting that it did things it didn't
Do you mean that you did the research, or your AI product did the research? How are you assessing whether a death was plausibly murder? So strange that the one example you find is of a car crash (one of the most common ways people die!) and no citation that it was found to be murder.
Interesting that you say you worry about re-creating the cluster from scratch because I've experienced exactly the opposite. Our EKS cluster required so many operations outside CloudFormation to configure access control, add-ons, metrics server, ENABLE_PREFIX_DELEGATION, ENABLE_POD_ENI... It would be a huge risk to rebuild the EKS cluster. And applications hosted there are not independent because of these factors. It makes me very anxious working on the EKS cluster. Yes you can pay an extra $70/month to have a dev cluster, but it will never be equal to prod.
On the other hand, I was able to spin up an entire ECS cluster in a few minutes time with no manual operations and entirely within CloudFormation. ECS costs nothing extra, so creating multiple clusters is very reasonable, though separate clusters would impact packing efficiency. The applications can be fully independent.
> ECS has weird limits on how many containers you can run on one instance
Interesting. With ECS it says for c5.large the task limit is 2 with without trunking, 10 with.
I've climbed the mountain of learning the basics of kubernetes / EKS, and I'm thinking we're going to switch to ECS. Kubernetes is way too complicated for our needs. It wants to be in control and is hard to direct with eg CloudFormation. Load balancers are provisioned from the add-on, making it hard to reference them outside kubernetes. Logging on EKS Fargate to Cloudwatch appears broken, despite following the docs. CPU/Memory metrics don't work like they do on EKS EC2, it appears to require ADOT.
I recreated the environment in ECS in 1/10th the time and everything just worked.
I was surprised to learn that PFAS are in dental floss, used to help in glide between teeth easily. This study linked using such floss and higher blood concentrations of PFAS: https://www.nature.com/articles/s41370-018-0109-y It's not strong enough evidence to suggest we should stop flossing, but they do make plain floss without PFAS, ex: https://www.amazon.com/gp/product/B005IHMXEQ/
Awhile back I encountered what I thought was hardware memory corruption that turned out to be a bug in the kernel [1]. Restic, a highly reliable backup program, is written in Go, and Go programs were highly affected [2] by a memory corruption bug in the kernel [3].