tcdent

I have looked into acquiring an ipv4 block many times but never came across this. Thanks for the lead!

Seriously. This idea that humanity has not spent millennia analyzing these concepts is pervasive in the modern world, and the only thing I can think to attribute it to is a lack of education. Not because I want to be insensitive, but because as soon as you start absorbing material and integrating the real timeline, you can't unsee it.

Not that they didn't start their research and development with a bipedal robot, but you can notice that over time they went from more abstract leg concepts to far more humanoid leg concepts.

That tells us that the latter (for their intended use) is a superior design.

I don't understand why this is considered a security incident. Human behavior incident, sure, but this is not a vulnerability.

Exactly. Being able to organize your code in a way that provides distinct responsibilities per crate is just good practice.

And then the ability to enforce a formalized layer between crates and the way that they assemble into your application (i.e. the public API) is powerful for comprehension and maintainability. I go as far as documenting each crate with its own README that presents it as a standalone component with usage instructions, much like an open source library, even if it's only ever used in a single system.

I recently used it for a Rust profiler which writes Parquet files, so DuckDB then gives an easy SQL interface for things like summarization, analysis, and joins across runs.

Aren't you really just talking about the level of abstraction being applied? If there are infinite possibilities between zero and one, then it's just our way of relating to it that imposes the perception of a limitation.

The easier and more secure way is to just inject sensitive credentials through a proxy service that ideally lives outside of the box in which the agent runs.

Because even if you're doing this in-memory replacement, the content still lives in they system's memory. So, it makes it less obvious to leak a credential, but it certainly doesn't prevent it.

Synthetic data, distilled data, etc., does not necessarily mean data coming from outside of an organization. When we see performance increases with models like Haiku, it is because they are able to leverage the knowledge of larger architectures.

I fully expect that we will see increased performance from smaller architectures (to a point) simply because they are refined using larger ones.

> The problem is if we can pack a Fable in Qwen 4 27B who will pay subscription prices?

This is available to everyone developing these systems. Prices per relative unit of intelligence will continue to decrease. And market economics will continue to drive the cost down.

I agree with you with one caveat. Professionally, your obligation is to be qualified for your job and ship work that you stand behind. Complete comprehension is absolutely necessary.

Personally, with side projects and tooling, go nuts. There's no reason to read all of that code.

The recent DeepSeek release used Opus 5 as a reference point as well. I don't understand it. It's not like they're referencing superseded releases of other open models.

CSRs that seemed like they had to be handled and approved by humans, and thousands of dollars in fees. We have come a long way.

What does it mean to "go into" math?

I'm all about the concepts you're presenting, but care to elaborate on how you think the corals relate?