Zambyte

Herdr is a harness aware terminal multiplexer, not a harness itself.

Car dependency is an excellent parallel. People buy cars on the promise that they should expect freedom of movement, but then they arrange their lives so they can only go where roads have been paved, and arrive where buildings have been demolished for parking lots. They become financially dependent on oil extraction in the Middle East. They become incapable of getting anywhere alone when they lose the ability to drive, due to ailments or age.

So why do we do it? Because we can't imagine living without the convenience of our phones.

Or have a tablet. That was my main reason for using Molly.

There is a very interesting divide in how people use AI to create things. The prevailing narrative focuses on a (large, to be fair) group of people who essentially use AI as a megaphone for their lack of care. It can be used by people as a megaphone to amplify the existence of care as well though. If you care deeply about making something, such as a tool to solve a problem or to make people happy, you can do really great things that people will appreciate. If you simply pipeline prompts from your head, to AI, to other people, without iterating on the output of the AI, you will annoy people with how loudly you don't care. That's slop, no matter how good AI gets.

I don't think the person you responded to has anything to do with ao3. They quoted the content of the update on the linked status page.

I had to check the spelling - they spelled "loser" correctly at least. Would have been a great irony if they didn't.

I have absolutely no insight into their financials, but yeah, their incentives point entirely to saying the funds are safe, regardless of if they actually are or not. Either they are indeed safe, and it eases panic, or Binance folds, and lying didn't matter. It's do or die for them right now.

> Codex, Claude etc already do subagent management on their own

What about together? Can you reasonably do agent to agent interactions across harnesses? herdr makes that easy.

One of my favorite reasons for using herdr is what I'll call "everything is a pane". Running a new agent? Runs in a herdr pane. sshing into a system? Runs in a herdr pane. Anything that runs in a herdr pane, your agents can interact with. I will often do things like ssh into a system in one pane, and then ask pi in another pane to help me do diagnostics on that system. It never has to try to ssh in directly in the harness with my credentials, it just sends keyboard input to the pane, and reads the content of the pane. I can watch the interactive session as it goes by.

Another workflow that I have sometimes is I'll kick off some work in an agent, and instead of making a new sub agent, I'll actually make a new parent agent if I get worried that it's going down an unnecessary rabbit hole. I'll tell the new agent something like "periodically watch the agent in pane X, it is working on Y but I am concerned that it is losing track of its tasking. Periodically review what it's doing, and make sure it doesn't go off the rails. If it does seem to be going off the rails, give it guidance to bring it back on track" and that seems to have helped.

Binance is centralized.

Well at some point they were.

"racing cars" actually would not be stationary. "Race cars" are the class of vehicle, which can be stationary. If the cars are racing, they are not stationary.

"High-speed" is ambiguous. It can be used to describe the class of vehicle, or it can be used to describe the state of motion of the vehicle.

In most languages, async is implemented as a special feature in the compiler, not as userspace code. You can't just jump-to-definition of async/await keywords in languages that use them. async/await are not keywords in Zig, they are regular function calls. There is obviously a categorically different level of insight between jumping to library code and digging into compiler internals.

It's all implemented as explicit userspace code that follows the same rules as the rest of the language. There is quite literally no implicit logic.

Exactly, so the title wrongly frames git as trusting certs that it shouldn't, when it's correctly trusting the system certs, and MacOS is wrongly trusting certs.

You along with everyone else was trying it. Hand crafted artisanal code wouldn't have stayed online either. Fluxer works now.