> Violet marks the data as it moves, always top to bottom. Nothing else on the page uses that color.

I'm seeing 3 violet elements on my screen. "ms" in the top left, the dot next to that text, and a dot on a horizontal timeline at the lower edge of the screen. Scrolling down I see yet more violet UI elements, I assume the one on the vertical timeline represents the data, while all the others represent... other things.

It seems violet is just the accent colour used for everything, which makes it an especially perplexing comment. I can only assume the "author" never even read the LLM's output before posting it.

▲

anon7000 5 hours ago | parent | next [-]

Yeah this smells like the type of comment an LLM leaves when it gets a really specific instruction. “use one consistent color for the data timeline. Right now we’re using multiple which is confusing.” Then the LLM writes some comment that’s a mini retrospective on what happened to justify itself.

▲

foolswisdom 5 hours ago | parent [-]

Claude seems to do this all the time. That, the empty words and the increased self initiative of claude were all reasons I decided to just use codex (now merged into GPT).

	▲	stratts 3 hours ago \| parent \| next [-]
		Codex does this too, I've noticed. LLMs seem to love documenting irrelevant implementation details in what should be user-facing text. I guess because the context is overwhelmingly the technical side of things, so without a later directive to steer it, that's what's most likely to come out.
	▲	pennomi 4 hours ago \| parent \| prev [-]
		Claude using documentation and comments as its personal diary is one of the most infuriating behaviors it exhibits. Half the time it’ll record some temporary implementation quirk, which later sessions interpret as infallible product design requirements. Absolutely unsustainable.

▲

taneq 3 hours ago | parent | prev [-]

Also “the clock at the top is exact” but the clock (on my phone, at least) is at the bottom. Still cool though!