dcchuck

In one of the earlier iterations of this they at least made the UX distinguish Codex vs. ChatGPT which I really enjoyed.

I must admit I spent a little time in ChatGPT this weekend, thinking I was in Codex. After some unexpected behavior (disappointed) I realized my mistake.

Yes - presuming the funds can’t earn SOFR+. The opportunity cost is the interest being earned elsewhere (minus interest earned taxes)

Curious what others use to store media for home/remote use.

I naively assumed my purchases from [company A] would mean I have permanent/immutable access. Even in the case of access not being revoked, I've found content itself changes over time. Usually related to jokes which have "not aged well" let us say.

I'm not here to champion leaving in that content. Or defend nostalgic rewatching. It just feels strange to not acknowledge.

Our team calls this "full three pepper blend" ;)

Same

This is great! Thank you :heart:

I enjoyed the sentiment, thank you for sharing.

Came to post about the site. My first reaction to the layout was "Oh, must be optimized for mobile." Then I clicked a link in one of the articles and it opened alongside it. Very slick. I enjoy this! It enables that "wiki deep dive" style of browsing. I suddenly want to read all your notes.

Hot Take: best $5k you've ever spent.

Imagine living your whole life thinking you couldn't do it?

I'm not saying it's fun. Just saying it may be a good thing.

I agree. We skipped CLIs and went all the way to TUIs because TUIs are "easy to make now"? Or maybe because claude/codex?

But in practice you are padding token counts of agents reading streams of TUIs instead of leveraging standard unix pipes that have been around from day 1.

TLDR - your agent wants a CLI anyway.

Disclaimer: still a cool project and thank you to the author for sharing.

I agree. The first paragraph on the page implies the javascript can natively search your machine (vs. via Browser Extensions)

They're also the only avenue to breaking out of the browser sandbox.

Yes exactly.

The problem is TUIs. Or at least the assumption you're only supposed to use a TUI. There are plaintext ways to invoke things but the advertised Claude/Codex experience is a TUI. You can't pipe the contents because it's not next - it's instructions to draw to the terminal.

<humor>TUIs are the new podcast! With everyone asking you to invoke tools via a TUI, there was nobody left to write actual tools.</humor>

TLDR - make sure you support plain text too ;)

This is a github pages feature. Given an account with the name "example", they can publish static pages to example.github.io

So this being from github.github.io implies it's published by the "github" account on github.

I prefer all my custom commands as 1 letter.

On my most frequently used machine/dev env this means -

e for vim

m for mise

n for pnpm

c for Claude

x for codex