1323
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Jul 2023
1323 points (98.7% liked)
Lemmy.World Announcements
28381 readers
1 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
Fwiw, it can be helpful to call out the date for such changes. Preferably in YYYY-MM-DD (ISO 8601).
While it's helpful to link to an off-site timezone converter tool (thanks for that, btw), "today" can be a different date, depending on where in the world you are. For example, Japan, Australia, and New Zealand.
Good point
Even better is "when this post is N hours old" :)
As someone who has had to grind through heaps of logs over the years, from systems in various timezones, from products that disagreed on the 'best' datetime format, I've become a fan of adopting ISO 8601 as much as possible. For personal systems such as a laptop, that's a different story. But if I'm spinning up an EC2 instance in
us-west-2
or a VM in Central Europe, I avoid the whole "err, what TZ is this in, or should even be in?" decision-making process and just run with WHO CARES IT'S SET TO UTC NOW LET'S MOVE ON ALREADY ๐And not that anyone here is likely to care, but here's a quick shout out to lnav - The Logfile Navigator for grinding on system logs (for systems where something like Prometheus or whatever hasn't been proactively set up).
ISO8601 is the only way to go.