kennethallen

Warrnambool is nice. Tower Hill is beautiful. I wouldn't want to leave there, either.

Don't forget that TLS 1.0 introduces itself as SSL 3.1, TLS 1.1 as SSL 3.2, TLS 1.2 as SSL 3.3. This hack you describe involves TLS 1.3 also pretending to be SSL 3.3, because ossified infrastructure freaked out at seeing "SSL 3.4".

Separately from the content of this paper, the LLM prose is unbearable!

These are not proper headers: "The Answer Neither Community Finished Alone", "The Peace Nobody Heard", "The Larger Disappearance". These are clickbait headlines. I don't want to be constantly tantalized--I want to be shown dense, organized information I can rapidly skim for the parts I care about.

That's an obvious example of the Claudese being spoken here, but it emanates from every word. Write your own paper or just publish the prompt and I'll run it in my own LLM.

Australia support, please! AUD15 limit?

Sorry, this kind of LLMglish is illegible.

  That rounding has teeth.

  Here is the answer, and it’s the most useful idea in this whole post.

  That last clause is the whole game.

The constantly referring back or forward to other Parts is very annoying. Please write your essay so that I can read it from beginning to end and it makes sense!

Also, this is far from "first principles". I have a general familiarity with GPUs but I had to look up a number of terms, like "LDS".

Looks like Blue Prince interiors. :D

I read this post and your post introducing zeroserve. One of the main parts of the original pitch was "no separate config file and scripts". Now you're adding a config file separate from the scripts. Is the pitch now that it's like Caddy but runs eBPF scripts in userspace?

These games all released with Denuvo on Steam and DRM-free on GOG. (Some of them have subsequently removed Denuvo on Steam.)

Mad Max Middle-earth: Shadow of War Deus Ex: Mankind Divided Yakuza: Like a Dragon

> This isn’t parser-style backtracking

How is this different from backtracking? You're doing a depth-first search over possible interpretations. The grammar is just expressed in the type system instead of usual spec formats.

Critiques in other comments are accurate. This is a tooling nightmare, but also probably a nightmare to read. Consider an expression like

  2026 March 10 to 13

What's the binding precedence? Does this mean March 10 through March 13, or midnight to 1 PM on March 10th? I think this breaks down outside of trivial examples that are better achieved in other ways.

What does this offer over feeding `-v` output into an LLM?

Extremely. Repo is littered with one-off Python scripts, among many other indicators.

And in every training corpus many times over.

Yeah, instantly switched to reader mode.

The fundamental reason JSON won over XML is that JSON maps exactly to universal data structures (lists and string-keyed maps) and XML does not.