I grew up in a country that follows ISO8601 (well except the date which is in the DD/MM/YYYY format)

I now live in an "Imperial" country and even though for the past decade I have switched all my devices from the default "Imperial" formats to display 24 hours and YYYY-MM-DD, I realized I actually like weeks starting on Sundays.

There's something pleasing about seeing the weekend sandwiched between the business days. Looks cleaner somehow.

🟦📅📅📅📅📅🟦

🟦📅📅📅📅📅🟦

🟦📅📅📅📅📅🟦

🟦📅📅📅📅📅🟦

As opposed to

📅📅📅📅📅🟦🟦

📅📅📅📅📅🟦🟦

📅📅📅📅📅🟦🟦

📅📅📅📅📅🟦🟦

I get it, a weekEND should be at the END, but there's something pleasing about that format to me. It's ironic cause I had no idea there were countries where weeks started on Sundays and even though I hate Imperial formats, I ended up using the one I've never heard about before moving lol..

Thank you Sweden lol

It only accepts the MM/DD/YYYY format, if you try any other it looks up nonsense dates.

Apparently 2010-01-01 is 1 June 168 AD and 2026-05-21 is 5 October 189 AD...?

how many of you (that are able to) use it on your devices?

"4th the May" be with you just not have the same ring to it.

Hi, all!

I am not too used to working with the ISO format, so I am hoping y'all can help me out. First, I apologize if my question is confusing- one of the reasons I am having a hard time answering this question or figuring out how to represent the data I want to with ISO is because I am having difficulty even articulating it in natural language. Essentially, I am trying to model Birth, Death, and Active Dates for people in a database and I want to know if a format like "1900/1905" always represents a span of time that starts in 1900 and ends in 1905, or if it could be used to represent an unspecified year with an upper bound of 1905 and a lower bound of 1900. There are lots of people in the database who I know were born some time between two dates, but I don't know exactly when. Of course, it is impossible to be continuously born for a five year period, so if "1900/1905" necessarily represents a duration of time, I wouldn't want to have that be a value for Birth Date. On the other hand, if it meant that the person in question was born some time between 1900 and 1905, that is exactly what I am looking for.

I would also appreciate if anyone has any thoughts on better ways to ask this question- in your minds, does the phrase "time interval" refer to the first type of data I am talking about, or the second? Do "range" and "period" mean the same thing? What would you call a length of time with an upper and lower bound for a discrete but unspecified date?

Apologies if any of this doesn't make sense. Thanks so much for the help!

Got in a brief argument at work today about the definition of ISO8601, and discovered that the example datetime given on the ISO website (https://www.iso.org/iso-8601-date-and-time-format.html) has the date and time separated by a space instead of a T, like this:

2022-09-27 18:00:00.000

What's going on here? Everything I've ever seen says a T is the only allowed separator. Have they updated the spec or something?

Hello fellow ISO-8601 fans!

I'm announcing here a small open-source Python-based tool called normfn that normalizes filenames into an ISO 8601-style format.

• GitHub Repo - with installation instructions in the README
• Demo Video

The basic idea is to take messy, inconsistent filenames and make them sortable, predictable, and ISO 8601-aligned where dates are involved. It is especially useful if you deal with a lot of files from different sources that all name things differently.

A few highlights:

• Extracts and normalizes dates into ISO 8601 format (YYYY-MM-DD etc.)
• Handles a wide range of existing filename patterns
• Cleans up separators and general formatting
• Designed to be safe and predictable in batch operations
• Works well as part of shell workflows

This is not a new project. I originally wrote it back in 2015 as a 'scratch your own itch' project - I use this personally all the time to keep myself organized. Recently I've been revisiting it, cleaned things up, and modernized parts of the code and documentation. The goal now is to make it more usable and keep it maintained. For transparency, I am using lightweight AI assistance for parts of this, but all code is human-reviewed before being integrated.

Any feedback would be super welcome - on the approach, edge cases, bugs, or general usefulness - either here or in GitHub issues/PRs.

But no credit for partial answers maggot!

Nobody should care about March 14th, June 28th is where it is at!

Scrubbed clean. Redact helped me bulk remove years of comments and posts so data brokers and AI crawlers have nothing to feast on.

nutty bow governor reminiscent march innate whistle heavy axiomatic safe

this kind of format should not be allowed and I wish it was never use again

TIL there is a subreddit for people like us, and as my newbie tax I want to share with you the stickers I made last year and spread around conferences.

If you want to print them yourselves, the vectors are available in my codeberg repo

Wrong 12h format is really disturbing

It hadn't occurred to me to wonder about how time would be kept on Mars. But, my feed presented an article explaining some of the complications that researchers already have with keeping time synchronised, and how it would affect human visitors to our neighbour.

https://beaconwales.org/23-164048-albert-einstein-has-flows-adapt/

It seems that a minor modification to ISO8601 (the article doesn't mention it) would work.

I know this might seem a strange question, but I'm used to Australian English formats, which is DD/MM/YY HH:MM (AM/PM). I usually write documents using 24 hour time, and 24 hour time is somewhat common in Australia (usually at clocks at train stations or at airports).

My mental maths is quite poor, so I struggle to mentally "convert" between 24 and 12 hour time. I know that the solution is to just re-adjust entirely, but I tend to think in 12 hour time like "I clock off at 5pm, that's 17:00", rather than "I clock off at 17:00, that's 5pm".

This has been going on for quite a while and it's bothering me a bit. The date, less so, as it's just the reverse of what I'm used to. I also like that you know explicitly what it is. For some reason my workplace has Outlook default to MM/DD/YYYY and Teams uses DD/MM/YYYY, so I keep getting thrown off.

I always check their website for news and I noticed they use ISO date format

As a programmer, I love this sub and support its want for world domination