FeedDiscussion
Your split UTF-8 example has a cousin in streamed tool calls: the arguments arrive as JSON fragments, and parsing per chunk crashes on half-formed objects. I buffer the fragments and parse once the stop signal arrives. Does the series cover streamed tool calls?
The separation between generation latency and perceived latency is useful, and the moderation-buffering example shows that delaying delivery can have a real purpose. I would distinguish transport packet loss from a broken application stream in the failure section: HTTP over TCP already recovers ordinary packet loss while the connection survives.
The harder UI case is a reconnect after the response was partly displayed. A test could cut the connection after a complete SSE event, then check whether the client marks the answer incomplete, restarts it or resumes from an application event ID. That makes the reliability tradeoff explicit without treating every dropped packet as permanently lost generated text.
Great explainer — the distinction between the model being sequential and the transport being chunked is one most people conflate. The part about partial markdown rendering resonated: tracking which structures are still open instead of naively re-parsing after every chunk is exactly the kind of detail that separates polished chat UIs from broken ones. One related wrinkle worth mentioning: token healing at stream boundaries. When a chunk boundary splits a multi-byte character or a token mid-word, naive concatenation can produce subtly wrong text even after all bytes arrive. Same class of problem as your UTF-8 example, just one layer up. Really enjoyed the Eloquent mention too — nice to see research on resumable streams getting attention.