tmalsburg2

Opus models after 4.8 didn’t work well with my homegrown harness, so I just skipped them until 5.5 which seems like a pretty happy match.

Nice!

> When context gets too long, maki compacts history automatically: strips images, thinking blocks, and summarizes older turns.

Don’t the summaries of older turns effectively invalidate the context cache, such that you consume less tokens but more expensive tokens?

I wrote my own harness in Emacs and it’s completely ridiculous how well it works. Auto-compact is the only missing feature on my list. Claude‘s approach, if I understand it correctly, invalidates a lot of cached context, and I‘m thinking about a more cache-friendly strategy.

Humans will not regurgitate longer segments of code verbatim. Even if we wanted to, we couldn’t do it because our memory doesn’t work that way. LLM on the other hand can totally do that, and there’s nothing you can do to prevent it.

Org-mode FTW

If the censoring is at the DNS level, can the admin please replace the domain name in the url with the ip address to which it should resolve? Thank you.

It actually interesting that Carlsen (likely the best classical player of all time) hasn’t overfit classical chess to the point where it hurts his ability to play other variants.

Sure, the market chose Markdown, but this simply led me to the conclusion that the market isn’t worth following. Of course the mismatch creates some friction, but the benefits of org-mode, for me personally, easily outweigh that.

Sounds smart but it’s abusing the semantics of “refine” and is therefore ultimately vacuous.

What problem is this trying to solve and does it actually succeed at solving it? I‘m struggling to see the appeal given that the JS still needs to model the internal structure of the template in order to fill the slots.

Also inflation.