• they/them

plural system in Seattle, WA (b. 1974)
lots of fictives from lots of media, some horses, some dragons, I dunno. the Pnictogen Wing is poorly mapped.

host: Mx. Kris Dreemurr (they/them)

chief messenger and usual front: Mx. Chara or Χαρά (they/them)

other members:
Mx. Frisk, historian (they/them)
Monophylos Fortikos, unicorn (he/him)
Kel the Purple, smol derg (xe/xem)
Pim the Dragon, Kel's sister (she/her)


irina
@irina
  • its not the best option for an internet standard time
  • it's not a good option for a replacement for hours and minutes
  • it is however, a good dumb feature for cohost plus to have

nex3
@nex3

now I'm sad this isn't a real system that people really use


tabatkins
@tabatkins

WAS SOMEBODY TALKING ABOUT A MORE OPTIMAL TIME SYSTEM

https://www.xanthir.com/b54c0 AND https://www.xanthir.com/hex/clock/

So base 10 is fine but if you really want to optimize your society's sense of arithmetic, base 6 is the way to go. 6 accords well with your native sense of "how many things can you count by sight", 36 is a reasonable approximation of "a largish group of whatever". 6 is highly composite, it's divided by 2 and 3, and 5 and 7 are one less and one more than it (which make them friendlier for arithmetic purposes). The times table is ridiculously simpler while numbers in the range you care about are only a digit longer at most.

Anyway, about time. Base 10 doesn't have a convenient way to divide the day up into hour-like, minute-like, and second-like divisions that are all the same and convenient to base 10. That's why our current system is 60/60/24, which is just nonsense (also it agreed with Babylonian numerology). The closest round base 10 number for seconds/day is 100k, which can't divide into three equal steps - you have to do something like 100/100/10, which gives inconveniently large hours. Going up to 1M (100/100/100) is just terrible - too many hours, minutes are small, and seconds are way too small. Going down to 1000 (10/10/10) is obviously unusable as well. Plus all of these work badly for dividing into thirds.

BUT IN BASE 6, whaddya know, a 36/36/36 division (aka 100₆/100₆/100₆) is about perfect. More hours than you're used to, but not ridiculously so, and they're 40 old minutes long, which is close enough to still serve the same purpose. Minutes are almost identical - approx 1m4s in the old system. And need second are about two old seconds, again close enough to serve the same purpose. (Bonus: 1 beat per second is now roughly the slowest rhythm perceivable by humans.)

Now that the three divisions are ah the same quantity, no more having to teach children the terrible "3 means 3am or 3pm, or 15 minutes or seconds, depending". 3 is 3 or 30₆, much simpler. And while 36 hours on one face is too many (just like 24 is too many), two hours hands works, so no more need for am/pm.

And now converting between time units is nothing at all. 3h22m is 322m (or 32200s) - you literally just move the heximal point.

Extra bonus: then we can reform the calendar too (https://www.xanthir.com/hex/calendar/), so months are also 36 days, so the perfect 100₆:1 ratio continues all the way from seconds to months. A year is then 10 months, of 6 6-week days each, with December (now back to being correctly named for it's month number) having a 7th week of 5 or 6 days.


nex3
@nex3

please elaborate on "two hour hands" though


pnictogen-wing
@pnictogen-wing

okay I'm just kidding. maybe we could find some other source of mostly-but-not-quite regular oscillations to reckon times and dates off.

like...I dunno, variable stars? "when can you pay me?" "when Mu Cephei drops below magnitude 4.5" or something like that?

I've gotten rather...allergic...to things that are too regular, too periodic

~Chara


You must log in to comment.

in reply to @irina's post:

most people (americans excluded, who seem to never know when asked) know of their local utc time offset

there's nothing i hate more than countries that use funky timezone names instead of utc. tf is eastern standard time bitch i'll kill you

story time. or anecdote time? maybe if it's interesting it's a story! anyway

in the ancient, forgotten past, i worked in the logistics industry, and there was a brief, doomed experiment with using internet time, or something like internet time. (it's been nearly two decades, so the details are fuzzy. "fingerprints on an abandoned handrail", as bob mortimer said.)

"why would the industry do that", you ask; "that doesn't make any sense", you say. and you're right. but you have to understand that logistics (specifically interstate freight) makes the timekeeping of DST (not all of the US observes it!) and time zones much more complicated.

thousands of trucks driving millions of combined millions through every time zone, through DST and non-DST cities/regions, and you need to know where all of them are, what time they got there, what time they'll get where they're going, etc. and you need to know all of that in the local time of their departure, in your local time, and in the local time of their destination, etc. if the origin, current location, and destination are each in different time zones, you need three different times for one moment in time—maybe more if you're not in any of those time zones or if someone outside of those time zones needs an update. for 10 or 100 trucks, it's not too bad; for 1000s of trucks, human and computer errors create cascading timekeeping accuracies.

so there was the aforementioned brief, doomed experiment to "standardize" time to internet time (or, as i said, something like internet time). a few companies' tracking systems implemented it. so, why was the experiment brief and doomed? because it's like that classic* joke** about a chain of translations. "that's just what we need, Niles—a fourth language!" all the experiment did was add "a fourth language" to the system, which confused most people and annoyed everyone. i think it lasted a week.

*I Love Lucy does the joke: https://www.youtube.com/watch?v=Xle3I-5nfpI
**Frasier does the joke: https://www.youtube.com/watch?v=Fe_IIyjiBJg

I've got an idea for worldwide time that makes sense to me

Keep the 24 hour clock, but replace the hours with 24 stupid words

"fumbo hour" "dumdum hour" "gerk hour" "plom hour" "plinkey hour"

and then everyone in their respective timezones will start to know what the stupid word is for each hour where they live

London: "It's 8pm? lmao that's gerk hour on the internet" Paris: "It's 9pm? lmao that's gerk hour on the internet" New York: "It's 3pm? lmao that's gerk hour on the internet"

Then you can say "let's do an internet thing at half past plom" and people will immediately interpret it as

London: "got it, that's 9:30pm here" Paris: "got it, that's 10:30pm here" New York: "got it, that's 4:30pm here"

that could functionally work by just picking a mildly-obscure-to-westerners language and using whatever the time is there in their language. so like just say oh it's chín sáng or hey we're gonna do a dungeon at half past một giờ trưa

(context: i don't use swatch, I use tenpo pi nasin ko aka Elementary Time)

imo the one benefit that swatch has over beeps (and to some degree, over UTC) is that swatch time has a notation that (I think?) can't be mistaken for any other time system I know of.

To explain:

  • if I say something happens at 3:20, 15:20, 3:20pm, 1520, etc, you don't know if I mean UTC, my local timezone, your local timezone, or potentially even boops, beats, or some other system.
  • if I say the time is @1520.34, I think swatch is the only system that uses that notation?
  • I can have the same certainty for UTC, I just have to specify 15:20 UTC, or 15:20z

though i could imagine folks leaving off the @ in swatch time just like folks leave off the time zone in UTC.

in reply to @nex3's post: