ahmedtd

> Is the throughput of these objects too high for etcd?

Yes (perhaps not etcd, but the combination of kube-apiserver and etcd)

Substrate does not use CRDs for anything on the hot path of actor scheduling or resumption.

> I don't get why they to restore the RAM of the agent env. Maybe to fully optimize resumption. Idk, I don't have that much RAM in my homelab, my agents use a ton, testing stuff in Chromium making screenshots for me. I can't keep RAM for 100 workspaces from the past 24 hours in RAM.

This is going to be decomposed. I believe the plan is to offer resumption with disk state only as well (and the RAM snapshots will need to be discarded from time to time, if you update the underlying code of the agent, or switch CPU types).

By the way, the RAM snapshots are not kept in RAM, they are serialized to disk, or uploaded to object storage.

Agent Substrate was built to provide a few (important) things over Agent Sandbox:

* More efficient usage of compute by timeslicing agents (Substrate Actors), which requires fast suspend and resume (using gVisor or cloud-hypervisor snapshots), as well as keeping the K8s control plane out of the critical path (so agents can't be stored as resources in the K8s database).

* Deep inspection of outgoing requests using an egress gateway

* Minimizing the exposure of credentials to unpredictable agent control (so they can't upload access tokens to pastebin).

Achieving those goals ultimately required a significantly different design from Agent Sandbox.

Substrate is in the process of being donated to the CNCF as a vendor-neutral common ground (similar to K8s). (The agent-substrate org is currently Google's, but that will change).

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)

From the article, it doesn't seem like Go is trying to re-encode strings? Go is saying (correctly, IMO) that a UTF8String field in the Issuer is not the same as a PrintableString field in the Subject.

Stock grants (RSUs, like Google gives out) are taxed as ordinary income at the moment they vest.

If you sell them immediately, then you don't pay any additional capital gains tax, because there were no capital gains from the moment you got them to the moment you sold them.

If you hold on to them, you will eventually pay capital gains on any increase in value from the moment they vested until the moment you sell them.

Perhaps, once they are vested, you could take loans against them, to get some cash while avoiding selling them.

But no matter what, they are taxed at the moment you receive them, and again at the moment they leave your possession.

American laws also have universal jurisdiction (for example, the Bill of Rights doesn't say, "unless you are located outside the US"). Most countries do not explicitly recognize that their laws do not have universal jurisdiction.

In practice, it is easy to pick out the situations in which there is "practical" universal jurisdiction, vs "theoretical" universal jurisdiction.

A Colorado company selling locally in Colorado falls in the "theoretical" bucket.

I don't think this is true. It's something that could be useful, with some sort of ACME-like automated issuance, but should definitely be issued from a non-WebPKI certificate authority.

If that's all you want to accomplish, you don't need WebPKI. Just generate a private key and a self-signed certificate.

(This is basically how Let's Encrypt / ACME accounts work)

Can you link your PRs here?

Kubernetes is such a huge project that there are few reviewers who would feel comfortable signing off an an arbitrary PR in a part of the codebase they are not very familiar with.

It's more like Linux, where you need to find the working group (Kubernetes SIG) who would be a good sponsor for a patch, and they can then assign a good reviewer.

(This is true even if you work for Google or Red Hat)

I have exactly the same two problems, haha. I wonder why they seem unable to fix them.

Sam Altman skipped any attempt to prove his own statements right, so...