zeroxfe

Distillation does not require access to weights.

> The discussion point is about each specific area.

I don't think it is. @squidmaster specifically noted, 'The "Renaissance man" era is long gone.'

Do you good understanding of where your food comes from?

How about the dollar you earned, spent, invested? Do you know how it works?

How about the clothes you wear?

This is just a tiny subset of the enormous complexity we're immersed in, and no individual or collective has a complete understanding of it. If you do, you're truly an outlier and GP's point still stands.

The page seems to be pretty clear that these are datacenters "owned and operated" by Google. They're not redefining "datacenter." The caches and edge PoPs are typically rented racks in partner datacenters, usually telcos and ISPs.

Selfies are used during live ID verification. (All of this is supposed to be encrypted, and destroyed within certain regulatory bounds.)

There is no perfect security. It's always flawed in some way.

Good security is extremely hard.

> because that's the definition of vibe coding.

That's _your_ definition of vibe coding.

I'm in that camp -- I have the max-tier subscription to pretty much all the services, and for now Codex seems to win. Primarily because 1) long horizon development tasks are much more reliable with codex, and 2) OpenAI is far more generous with the token limits.

Gemini seems to be the worst of the three, and some open-weight models are not too bad (like Kimi k2.5). Cursor is still pretty good, and copilot just really really sucks.

I've done this kind of thing many times with codex and sqlite, and it works very well. It's one prompt that looks something like this:

- inspect and understand the downloaded data in directory /path/..., then come up with an sqlite data model for doing detailed analytics and ingest everything into an sqlite db in data.sqlite, and document the model in model.md.

Then you can query the database adhoc pretty easily with codex prompts (and also generate PDF graphs as needed.)

I typically use the highest reasoning level for the initial prompt, and as I get deeper into the data, continuously improve on the model, indexes, etc., and just have codex handle any data migration.

Expiries are a defence-in-depth that exist primarily for crypt hygiene, for example to protect from compromised keys. If the private key material is well protected, the risk is very low.

However, an org (particularaly a .mil) not renewing its TLS certs screams of extreme incompetence (which is exactly what expiries are meant to protect you from.)

> Also MCP is very obviously dead, as any of us doing heavy agentic coding know.

As someone that does heavy agentic coding (using basically all the tools), this is so far from the truth. People claiming this have probably never worked in large enterprise environments where things like authentication, RBAC, rate limiting, abuse detection, centralized management/updates/ops, etc. are a huge part of the development and deployment workflow.

In these situations you can't just use skills and cli tools without a gigantic amount of retooling and increased operational and security complexity. MCP is really useful here, and allows centralized eng and ops teams to manage their services in a way that aligns with the organizations overall posture, policies, and infrastructure.

> Google is so far behind agentic cli coding. Gemini CLI is awful.

This part I totally agree. It's really hard to express how bad it is (and it's really disappointing.)

> TBH I would have just rendered a font glyph, or failing that, grabbed an image.

If an LLM did that, people would be all up in arms about it cheating. :-)

For all its flaws, we seem to hold LLMs up to an unreasonably high bar.