Private
Public Access
Everything is stored and server-rendered in UTC (config.settings.base's TIME_ZONE), so article times, the article detail header, and the dashboard's "last fetched" column were always showing UTC regardless of where the viewer actually is. Article/feed timestamps now render as <time datetime="..."> elements carrying the UTC instant plus a UTC-formatted fallback as their initial text; static/js/localize-times.js reformats them using the browser's own timezone via toLocaleString(), both on page load and after every htmx swap (pagination, the inline article expand, the dashboard's retry action all inject new <time> elements without a full page load). No server-side change needed — this doesn't touch the (currently unused) per-user timezone field, and works correctly even if the viewer travels or changes their system timezone, with no settings page required. Verified live in the browser against a UTC-stored timestamp rendering correctly shifted to the sandbox's local zone. Known related issue, out of scope here: the stream's "Received today/yesterday" date-group headers (apps.reader.views._group_by_date) are still computed server-side via timezone.localdate(), which is also effectively UTC — an article just before/after UTC midnight could land in a date group that doesn't match its now-correctly-localized time-of-day. Flagged for the user rather than fixed, since correcting it properly would mean moving date-grouping to the client too. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>