969 karma · joined November 29, 2011
Chief Excel Officer, MAD* Scientist, Pythonista, Rustacian, PRQL Core Contributor (: ML, AI, Data)
* twitter: [@T0bias_Brandt](https://x.com/T0bias_Brandt) * github: [@snth](https://github.com/snth/) * [PRQL](https://prql-lang.org/)
There's a reason i read HN and not LI.
I have a bunch of Claude Code Plugins and yesterday asked Codex to make them accessible to itself. It wanted to rewrite most of it. I was hoping i could get by with some symlinks or something to avoid drift.
My sense of the Sutton Dwarkesh interview was that he was calling out that he didn't mean just longer datasets, but rather learning through exploration and that's exactly RL.
Interesting
For learning ClearFlow, I used the Games app available from the "Clearflow Games" section on their website: https://clearflowkeyboard.github.io/
I also have the issue of the thumb getting in the way so I spent a couple of days playing the games to get my layout memory up and then it became usable without frustration and I'm not looking back now although I occasionally still forget the odd letter location.
I'm happy with the switch. Like any keyboard switch (I've gone from Qwerty to Dvorak and now a Colemak-dh derivative with about ten years on each) it takes some time to learn the layout. Overall I'm happy with it though and there are less frustrating misinterpretations and corrections needed.
This post was swiped on it with only two corrections and the second one was my fault as i misremembered a key location.
Actually i think it's the "for" in the title that's at fault. The repo title is quite clear, but the submission title is ambiguous to me.
Transducers are just the morphisms in the category of the reducing-functions. No problem!
From a cursory look my impression is that it deviates from git too much and therefore I can't use my git knowledge to predict how it will behave. I'm quite rusty on git internals but afair .git/refs/ is great because you can do what you like in there but the downside is that it doesn't hook into the rest of the git structure.
So how does this work with branches, worktrees, etc...? Having a jsonl message log in .git/refs/h5i/msg seems very linear. Presumably you store commit refs in the json obj or context dag, but what if I rebase the branch and the original commits are dropped because they're not referenced anymore? Or say I follow the conversation and want to rewind a few messages and branch from there in a separate worktree, how does that work?
Your repo README does say:
- "It uses dedicated refs, so it doesn’t pollute your working tree or your normal branch graph."
- "Because these are Git objects, they are content-addressed, deduplicated, pushable, fetchable, and survive `git gc`."
- "Because the log lives in refs/h5i/msg, a conversation survives clones, machines, and branches — it travels with h5i share push / pull, and divergent sends from two machines union-merge with no message lost."
Therefore these look like design decisions and it would be nice to understand them better.
My first instinct would be to put most of what you have under .git/refs/h5i/ in a .h5i folder in the repo itself and manage some shadow branches under .git/heads/.h5i/ with multi-parent commits pointing at the context commit as well as the previous h5i message commit along with some hooks to handle rebases etc ... . That way battle hardened git machinery gets used and more importantly to me, I can leverage my existing git knowledge to understand dependencies. That would go against your "it doesn’t pollute your working tree or your normal branch graph" goal but I'm of the "explicit is better than implicit" Python school so I like to have the details exposed as long as I can filter them out easily (or by default).
$ curl -O https://raw.githubusercontent.com/snth/radar/refs/heads/main/radar
$ chmod +x radar
$ ./radar snth@bsky.social
[RADAR] Scanning for snth.bsky.social...
[RADAR SCREEN]
User: Tobias Brandt (@snth.bsky.social)
Status: Active
Last Seen: 2026-05-28T19:42:15.865Z
--------------------------------------------------
Just vibe coded a 60 line POSIX script Bluesky client in the style of `finger` of old:
github.com/snth/radar
--------------------------------------------------
If you wanted to be more authentic to the original you could implement a custom Lexicon.Semitic people - Wikipedia https://en.wikipedia.org/wiki/Semitic_people