There was extreme media coverage of the helicopter, live streams, twitter accounts, and scientists talking every day in media about if they could get another flight out of the copter. It was a huge media moment

All american models refuse to help me design nuclear weapons in Nuclear Design Bureau or to work on my cybersecurity projects.

They offer ZDR. It was effortless to get.

that's not blocking though. It's allowing you to skip over the areas people commonly skip in videos where they take the data from everyone. I get them at sponsor slots of course, but also intros often. Because it's not removing it entirely, I would not consider that blocking.

The parent’s characterization is fine. 9/10 times (more in my own experience) it is the functional equivalent of a sponsor blocker. That it technically isn’t that specifically is immaterial, because if it works, that’s because people are skipping the sponsor segments in large enough quantities for it to easily become that.

That said, I don’t think YouTube owes it to Premium subscribers to add a sponsor block. That’s part of the video’s content as it was provided to YouTube, and YouTube never advertised YouTube Premium as something which will block in-video sponsor reads. This is part of how YouTubers make a living & a Premium sub doesn’t replace the money they receive for those the way it does for YouTube’s own ads.

If you are approaching anything looking like an enterprise environment, you are likely to have Kubernetes nearby. ko is a weird requirement. ax requires agent substrate, so it makes sense that it's needed. Agent Substrate also has experimental support in kagent, so it makes sense that it is growing.

I don't really like the oversubscription of agent pods though, as you can no longer trust the k8s pod identity as being from a singular workload. Haven't seen a solution to this for ax yet and it is a barrier to adoption for us.

Agent Substrate is solving this - similar to K8s, Substrate is an OIDC (and also SPIFFE) IDP. Credentials containing the actor's identity can be injected into outbound requests using the Substrate egress gateway.

(This is work in flight, but it will land within a few weeks)

Googles Agent Identity is already built around SPIFFE but others are not.

I believe the substrate egress-gateway needs to handover the internal SPIFFE one to an external system (e.g. Entra Agent ID). Not sure if that should be part of substrate or kagent/ax/..

What exactly is the difference between that and 50 states having their own regulations?

The absence of a central bank.

yes they do, it hurts their image more directly if you claim it's you.

So why do it then? Just to sabotage their own country? That makes no sense.

It makes more sense that this is a continent wide action taken by Russia, considering the similar event in France just a few days ago.

no? if you are diligent you can say nothing and people will hopefully attribute it to your enemies and you get off with your own ploy of looking peaceful and harmless

In which case what do they gain here?

You can claim ownership via restricted channels, e.g. a phone call to key politicians, and rely on their self-interest to keep things quiet while understanding the threat.

In some cases, if the action is a bit too effective, you might even want to avoid it being pinned on you. Al Qaeda occasionally refused to claim ownership of things they very plainly did, and the Russians do it very often (e.g. when they shot down a Dutch passenger plane a few years ago).

The iPhone Air is an absolutely beautiful product.

it pretty explicitly does, it just means you don't like them.