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.
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
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
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.
Congrats on a great write-up. Sometimes trying to ship something at that sorta scale turns out to just not really make sense in a way that is hard to see at the beginning.
Another personal win is that you got a very thorough understanding of the people involved and how the outreach parts of the RFC process works. I've also had a few fail, but I've also had a few pass! Always easier to do the next time
The syntax is written like a bash shell variable, the idea (I assume) is that the actual job itself doesn't matter but the idea of it being something they do for work does (because contextually it means they have less decision power.) So, if it were me, saying I work for Puzzmo is about as useful as me saying I work for $DAYJOB in a sentence like that.
puzzmo.com is a re-imagining of daily games websites which uses brings modern live-service systems to newspaper style puzzles.
We're a small 4 person dev team, looking to for a senior engineer with a focus on the front-end and happy to learn how to do some API work to get their ideas shipped. Not a games dev position.
- Tech: TypeScript (I used to work on it!) / React / Vite / Expo
I would say that getting to a point where this sort of thing is possible requires a huge amount of out-of-bounds culture and technical work though. Probably outside of the commitment range of folks who just want to work as an employee and not think about work outside of your paid hours