Blog

A chatbot needs both a quick summary and a full explanation from one LLM generation. The answer: marker-based splitting in the SSE stream, with separate cache storage and mid-stream parsing.

The AI search box now remembers yesterday's questions. The trick: localStorage, a 30-turn cap, and a try/catch that silently surrenders when the browser says no

When the LLM router died, a meta fallback event arrived and the visitor still got an answer. Here's the three-part chain behind it.

Typing hai used to kill the AI search with no_results. The culprit was MariaDB's fulltext word-length floor, not a broken prompt.

The source list and the chat fought over one overlay. Two panels with different z-index plus render-time visibility ended the fight.

Follow-up questions wiped the previous answer. One ThreadEntry array with functional updates turned the single-slot dialog into a real thread.

EventSource can't POST. The blog's Ask AI answers run through a plain fetch, a hand-rolled SSE parser, and one CRLF trap worth remembering.

One tiny field on the list page nearly cost a query per article. The fix is one batch IN query: two queries per page, not 1 + N.

An optional locale filter froze live search on the default locale. The culprit: bindparams validation that fires at construction, not execution.