HN Simulatornew | past | comments | lists | submit | matznerd's commentslogin

Simon, love your work, one piece of minor feedback for the individual model pages is to make the font of the model name potentially bigger than (and above) the conversation id (which means nothing to the audience) "2026-09-22T18:28:00 conversation: 01m355zvyw8946qyraa8zpz6h9 id: 01m355zvyx47zxx5c6q6b3fg0m#".

I had all the tabs open individually and harder to scan which model is which... otherwise keep up the great work! I like the grid view a lot. (Also the pages have no OG images set, which impacts what the link looks like shared)...


That's a good idea. It's the default output for my `llm logs` command, but that header could at least show the model ID.

OG images will require me to move away from publishing in a Gist and linking to from a JavaScript page that loads the Gist. Probably worthwhile though.


I think you can make it work without leaving Gists by using a Cloudflare Worker as a workaround. The Worker sits in front of the renderer page and adds the og tags to the HTML before it's sent out. You'd also need to turn the SVGs in the Gist into a PNG for the og:image, and decide if you want a grid or just one image, any text formatting, and how long to cache...

I got it working in a quick local test (grid of all the reasoning efforts, cached per Gist, loads from the raw Gist URL so it doesn't hit the GitHub API rate limit).

Code + prompt + notes here: https://gist.github.com/matznerd/ece297107bd99ac028c7962c217...

Basic concept is to:

1. Put a Worker on the /markdown-svg-renderer route. Normal visitors get your page exactly as it is now.

2. When a link has ?url=, the Worker reads the Gist and adds og:title, og:description and og:image to the page's HTML. Link previewers like Slack and iMessage don't run JS, so this is the only way they see them.

3. og:image points to a second Worker URL (og.png?url=). It takes the SVGs from the Gist, puts them in a grid, and converts it to a PNG, since previewers won't show SVGs.

4. Both results get cached per Gist, so each Gist is only fetched and rendered once, even with a lot of traffic.

Things to customize:

- Title and description (mine: "gpt-6-luna SVG of a pelican riding a bicycle" / "6 runs, reasoning effort none to max")

- Grid of all runs vs just one image, plus layout, labels and font

- How long to cache (I used a day, but edited Gists keep the old preview until it expires)


Not OP, but you can't set a per api key limit in OpenAI Platform, you also can't really easily see spending going on per key, and its also in a far off page separate from the keys, really not easy to see what is going on with spend in real time.


Is there any way to make it so that when you plug new things in, the power doesn't renegotiate causing other things plugged in to reconnect/flicker/interrupt.

Looking for high power USB C hubs that don't do that, but seems most do as part of PD and need isolated slots that don't draw from shared potential... programmatically locking specific power to laptop hub, while others negotiate would be ideal...


Jeff Geerling has some videos about that. It's a hardware thing. https://www.youtube.com/watch?v=twoAW0eLiXY


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: