Flipping over 2025 and getting ready for 2026. #86
Conversation
…to next year. Having people go to the archives view first. Adding winners for 2025. 🎉 Victory
| const hackweekDate = new Date('2026-08-17T00:00:00'); | ||
| const difference = hackweekDate - new Date(); |
There was a problem hiding this comment.
Potential bug: Countdown timers now use a date string without a timezone, causing them to resolve to the user's local time instead of a single global time.
-
Description: The application's countdown timers were changed to use a hardcoded date string,
2026-08-17T00:00:00, without a timezone specifier. Both the nativeDateconstructor and themoment.jslibrary interpret such strings in the user's local timezone. The previous implementation contained logic to synchronize the countdown to a specific moment in Pacific Time. As a result of this change, users in different timezones will see the countdown end at different absolute times, which can cause significant confusion for a globally coordinated event like a hackweek. -
Suggested fix: To ensure the countdown is synchronized globally, modify the date string to include a timezone. For example, use an ISO 8601 string with a UTC designator, such as
'2026-08-17T07:00:00Z', to represent a specific moment (e.g., midnight Pacific Daylight Time). Alternatively, restore the logic that dynamically calculates the target time in a specific timezone.
severity: 0.7, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.
nikolovlazar
left a comment
There was a problem hiding this comment.
LGTM! I do like the idea of redirecting to /years post-hackweek. Thanks for making these changes @jmanhart!
Changes
/projectsto/years