Hacker News new | ask | show | jobs
by FloorEgg 173 days ago
My guess is that including timestamps in messages to the LLM will bias the LLMs responses in material ways, and ways they don't want, and showing timestamps to users but not the LLM will create confusion when the user assumes the LLM is aware of them but it isn't. So the simple product management decision was to just leave them out.
3 comments

That's no excuse imho. I see 2 different endpoints, 1 for llm stream and 1 for msg history (with stamps). New timestamps could be added FE as new messages start without polluting the user input for example
How many years experience do you have managing products with millions of users?
I'd bet this is correct. I'd also bet you've worked on user facing features.
I could definitely see that being an issue, but like with so many UX decisions, I wish they would at least hide the option somewhere in a settings menu.

I also don't think it would be impossible to give the LLM access to the timestamps through a tool call, so it's not constantly polluting the chat context.

Adding any unnecessary content to the context decreases inference quality.