January meeting is shown as 'Past Event' even though it is scheduled for later today

[nereye]

At the time of this writing (01/20/2026, 02:18 PM), the January MicroHAMS meeting has not happened yet (being scheduled for 01/20/2026, 06:00 PM to 08:30 PM), but is being listed under 'Past Events' in the website.

[nereye]

The cause of this bug seems pretty clear, the code in src/pages/events/index.astro is using JavaScript's Date constructor and passes in a date, this interprets the date as UTC and it all goes downhill from there.

From https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date#date_time_string_format:

When the time zone offset is absent, date-only forms are interpreted as a UTC time and date-time forms are interpreted as a local time. The interpretation as a UTC time is due to a historical spec error that was not consistent with ISO 8601 but could not be changed due to web compatibility.

Long term, we should switch to a sane API (Temporal: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Temporal), however Temporal is not yet supported on all browsers (https://caniuse.com/?search=Temporal) so in the meantime there seem to be two options:

1. use a polyfill (e.g. https://www.npmjs.com/package/@js-temporal/polyfill), or
2. work around the issue like we already do for the date formatting elsewhere in the site

[radiolabme]

Probably better to use a polyfill and try to get out of the business of date/time formatting where we can. What do you think?

[nereye]

Agreed. Will start testing a possible solution along these lines.