inem

ChatGPT renders every message in the DOM at once. At 2,000 messages that's ~500K nodes. The tab freezes or crashes.

The AI handles long conversations fine. It's purely a frontend problem — React re-rendering an ever-growing tree.

The fix is simple: intercept the fetch response for /backend-api/conversation/{id}, truncate the mapping to the last N messages for rendering, keep full context for the model. 30KB, no dependencies, no external requests.

I built this because my most useful conversations were becoming unusable. Chrome Web Store submission is pending review, so distributing via Gumroad for now.

Happy to answer questions about the implementation.

RestructuredText seem to me like an alternative to Markdown.

Hamdown idea is to enable automated content-generation by allowing ruby code embedding (like you can do with HAML)

Hamdown author here. To make it clear the I don't see this as a replacement for HTML/ERB/whatever templating solution for your web app.

The niche is rather narrow - it is for people who use static site generators like Jekyll/Middleman, and write content mostly in Markdown.

I often simply want to do a quick look-and-feel experiment by styling some of the elements with Tachyons. This is where Markdown becomes a bottleneck.

Another idea is to make front-matter a first class citizen of Hamdown so that you could add a bit of structured data on top of your blog post and use on the page.

P.S. You kinda can achieve this with kramdown, but I find its syntax super-weird.

You're welcome! :)

Well, not really :) But it is definitely inspired by crontab.guru

Thanks! That's true. And it is pretty annoying, because regular developer has no chances to remember all the shortcuts.

Actually after we started working on it, we found five projects, attempting to solve the same problem: foragoodstrftime.com, strftime.org, strftime.net, strftimer.com, strfti.me

None of them were ideal though. We analysed them, took the best parts, threw away the worst - this is how strftime.guru appeared.