Dev here: Keytrace lets you verify other accounts like Keybase does (e.g. public proofs of identity) but doesn't orient the connection on GPG. Instead uses an atproto/bluesky account as the central source of identity, and stores everything in atproto.

So you could think of it as a simpler, de-centralized version of the Keybase identity proof system.

I'm linking my keytrace.dev: did:plc:t732otzqvkch7zz5d37537ry

Interesting project! Added it to my list of TypeScript derived languages: https://github.com/orta/awesome-typescript-derived-languages

This is a cool idea, I really enjoyed crashing at other companies offices for short periods - glad to see a company systematising that

OP here, luckily in this case, it means a more supported and vertically integrated alternative. Which does have less features, but actually gets bugs fixed and keeps up to date with the platform - so it's a net win overall IMO

Thanks, your work was of huge value to me, way more than you were rewarded for, sorry :/

That was a fun read, nice work

With Claude Code at least, all of the chats you've had are stored in jsonl files on your computer in ~/.claude - I made a little TUI for exploring these in https://github.com/orta/claude-code-to-adium

Personally, I'm less sold on tracking prompts as being valuable both for production cases (imo if a human should read it, a human should have wrote/fully edited it applies to commits/PRs/docs etc) and for vibe cases where the prompts are more transitory

Thanks yeah, your post hit the nail on the head so well I got to delete maybe a third of my notes for this!

This is an excellent insight

tsc's code is mostly the type-checker, you want to look for a "transpiler" here, so embedding either swc, esbuild, sucrase or the like to handle the process of converting for you. I've never heard of one written in C++ but that may exist.

swc exists as wasm which any browser should be able to execute.