
Tired of these DPRK hacks. So I built the ultimate defense. DPRKaptcha[.]com Simple questions with existential outcomes (for them). Live now to protect the internet from North Korea.
✓@megaeth | @modernmarket_

Tired of these DPRK hacks. So I built the ultimate defense. DPRKaptcha[.]com Simple questions with existential outcomes (for them). Live now to protect the internet from North Korea.

Biggest surprise in all my travels is how much I've grown to love distinctive architecture. The sheer scale and grandeur of Florence and Vienna. The intricacies of Alhambra palace. The organic modern combo of Singapore. And now the craftsmanship of Japanese temples.


I take it back. Has to be visual for agent->human. So text+graphics. The bandwidth our eyes can achieve relative to ~all other senses isnt even close. So, humans talking to agents and agents visually presenting responses back is my final answer.

The final agent interface will be voice in both directions. Can be to a single "chief of staff" agent or an ephemeral "chief of staff" personality which is made consistent through separate contextual interfaces. Only level behind that is nuerolink embedded

Just watched @jinfizz drive an ADE from his iPhone Duo and I can't help but think foldables are going to be the new remote workstation.

T3 Agents rewrite going well. Kept it byte-for-byte and gained substantial mem., CPU and speed improvements even at swarm scale (16k subagents). Went from Typescript+node to Rust and experimented with swapping terminal UI for Rune but it didn't net-out to much so killed that.

Fluffy French toast acquired. 8/10. Had almost a mochi-like chew to it but was still very light. Fluffy pancakes next.

I'm noticing a "headless" trend. Definitely for software, but also for businesses. AI has made software so malleable that it doesn't make sense anymore to draw rigid lines between your offerings and others. If you build the right way, Agents allow for all of it to take the shape your customers want. I expect this trend to continue.

Highly recommended list. Omabox in particular has been a game changer for my iteration pace.

For those suggesting to just do model routing in CLAUDE/AGENTS files: It's a level too deep.

"Why not just add this to Claude[.]md?" Because it isolates the logic to Claude. If you use multiple providers then you'd need to replicate the logic in every harness' Claude/AGENTS file. Doing it in T3 sets it once for any potential provider + surfaces the routing logic.


Left all machines at home while I travel, but plan to max all subs via T3. First is a perf rewrite of the T3 Agents dashboard I created. → Rewrote the core in Rust → Explored a Rune FE but turned out to be ~no improvement over terminal FE so scrapping → Testing swarm-level scale (~16k active subagents) while losing no perf I think the one thing lacking right now in T3 is subsystem observability, which I aim to fix with T3 Agents.

Also happens when I spend time with my neighbors. Mostly local workers w/ normal office jobs + healthcare. They're either not using AI at all or have it tune spreadsheets. The world is still in pre-clawdbot era
