I keep the Live Help page permanently open in a browser tab and review it for new help requests periodically throughout the day. Unless I do a full page refresh, the local time that is displayed when I hover over a user's avatar is the local time at the time I last reloaded the page. If I click the blue button that shows up to view new posts that have come in, the local time displayed for the new posts are accurate (for a minute) while all the other times displayed remain inaccurate, still based on the last time I did a full page refresh. I don't think I should have to continually refresh the entire page in order to see the correct time for a user. I would think that, upon hovering over a user's avatar and the UI opening the popup, the code could take the user's time zone (which is known) and apply it to the current time (which the browser knows) so that every single time I hover over a learner's icon I get the correct current time in the learner's time zone.

I'm attaching images showing the learner's local time being out of date with my clock, and it still being out of date when hovering over the learner's avatar 2+ hours later.

Although I've focused on Live Help above, it's broken in various places (perhaps all places). E.g. in the Tutors community channel at https://schoolhouse.world/dashboard/community/c/199? there is the same behavior. When I click a button to load new posts, those new posts have the correct local time displayed (for a minute), while all prior posts have the incorrect local time, unless I do a full page refresh.

Looking at the graphql API response (this call gets triggered when I hover over the user's avatar), the IANA identifier for the timezone is already being returned, e.g. "timezone": "America/Los_Angeles", so it seems like it'd be straightforward to use that to generate the proper local time, without requiring any new data to be returned from the backend.