
ALT I’ve worked on event websites. For those, I think the best strategy is to store the datetime twice: once as a local (without timezone) yyyy-mm-dd hh:mm style thing and then again as a denormalized version in UTC. You also need to store the location timezone of the event. The UTC timestamp is there to power features like “sort by date” and “what’s happening in the next hour”. The local timestamp is there for exactly this problem: if a user sets up an event at 6pm on November 25th 2025, they mean 6pm LOCAL time, no matter whether legislation or other weird events have changed the DST rules for that location. DST rules change with little notice a lot - just take a look at the amazing tz mailing list: https://mm.icann.org/pipermail/tz/2024-July/subject.html Here’s Ukraine canceled DST in autumn of 2024 Parlament of Ukraine decided to cancel introducing DST, so, starting from spring 2025 DST will not be used for Kyiv time zone. Occasionally that mailing list has changes that are made

ALT a bingo card with * WTF is detached HEAD state * I hate git * git's design is so elegant * I've used git for 10 years and I have no idea how it works * commits are immutable snapshots * just use magit * git is a directed acyclic graph * you have to understand the linux kernel dev workflow * mercurial is better * git is not github * subversion was so much worse * I only know 5 commands * a branch is just a pointer to a commit * the CLI is badly designed * you should just read Pro Git * rewriting history is bad * just spend 15 minutes learning git's internals * something about "porcelain" * merge sucks, only use rebase * rebase sucks, only use merge * I just do not care how git works * content addressed storage * subversion was better * something about Linus Torvalds * I just delete my git repo if I mess it up




























