if you're going to try to format a datetime in a mathematically logical way, it has to be in the format of
2019-05-04 20:51:35
with whatever dividing punctuation you like
literally anything else and you might as well do whatever the hell you want, quite frankly
@InspectorCaracal the opposite, 35:51:20 04-05-2019, might also make logical sense, but looks absolutely ridiculous
@InspectorCaracal nah, it's definitely going [smaller unit][bigger unit]
seconds in front just looks weird though
@troubleMoney no I'm saying that 35 is thirty five, not fifty three
@InspectorCaracal ah, right, gotcha
considering we're already using 60 seconds/minutes and 24 hours instead of 10 or 100 if could be said that we've already broken the logic so ordering it small to big isn't much of a leap, deffo use yyyy-mm-dd HH:MM:ss because it reads better though
@troubleMoney i'm not saying there is one perfectly logical ideal solution, i'm saying that if you're going to make a mathematically logical timestamp, specifically, as your goal, it has to be in that order
I have no problem whatsoever with people using other formats of timestamps - in fact, I tend to prefer human-usable to mathematically-logical - but if people doing that are going to claim it's because of ~math~ or ~logic~ then imo they're full of shit
@InspectorCaracal let's just use epoch time, no need for ordering stuff in that one!
@troubleMoney lmao there we go
@troubleMoney our entire numeric system is predicated on the basis that the first digit is the largest and the last digit is the smallest
therefore, a timestamp as a numeric must have the first digit be the largest and the last digit be the smallest
@noelle @troubleMoney ...
........oh goddammit ellie 🤣
@troubleMoney see it doesn't because each of the parts goes [larger unit][smaller unit] so you're going, like
21436587