Mastodawn

Oh god someone is going to explain to me why this isn’t a bug, aren’t they?

Sigh.

stibbons 6d ago

@futzle Hey did you know time zones?

@stibbons How about you explain them to me as if I have never experienced them before? Use Forth as the example language.

stibbons 6d ago

@futzle The only Forth I have written in anger was pbforth for lego mindstorms. brb minifig interpretive dance incoming.

neoluddite 5d ago

@futzle the real bug was the bug in our brain all along

I love this, so I 6d ago

@futzle leap years were a mistake

lick here for more info 6d ago

@jpm think he just posted it about 8 hours short of 10 years apart.

And to be fair, the post does say "today", not "now"!

sorry for doing the thing you said we would do @futzle

@virtulis @jpm Indeed, it emerges from confusion of date arithmetic with datetime arithmetic. Also time zones are a factor in date arithmetic.

I love this, so I 6d ago

@futzle @virtulis we would not have this issue if everyone used hyperlocal solar noon as their display time

Magnus Ahltorp 6d ago

@futzle @virtulis @jpm Time zones should not be a factor when calculating how long ago something is, should they? 1 hour is 1 hour, even if we are in different time zones. I'm guessing the HCI problem here is that "year" is not a useful unit to truncate the decimal part of.

@ahltorp @virtulis @jpm I said time zones are a factor in date arithmetic, not in datetime arithmetic. This moment now is 17 March for me and probably 16 March for you. If we do date arithmetic on a now() timestamp, you and I will get different results.

Steveg58 6d ago

@futzle
Sounds like a bulk standard off by one error.

marzuq märzenbecher 6d ago

@futzle ~all~ are - it’s mastodon <3

Colin 6d ago

@futzle I think you’re allowed to tune out JavaScript apologists.

Juffo-Wup 6d ago

@futzle

Well, there was this accident with a time machine, a lot of whipped cream and several kittens...

JP 6d ago

@futzle I saw the same thing and had a giggle.

Paul McEwan 6d ago

@futzle Time looks okay for me.

@PaulMcEwan Could be because we are in different time zones. Or it could be we’re using different clients which display “ago” time differently.

Paul McEwan 6d ago

@futzle Could be. I'm always VPNed to Aotearoa so I'm slightly in the future.

thinkberg 6d ago

@PaulMcEwan @futzle Even then ...

Morten 6d ago

@PaulMcEwan @futzle Yeah but just one year from now it's going to be all fucked up again.

Bellycan 6d ago

@futzle grateful that the web version (on fosstodon.org at least) doesn't even attempt it.

Ygor 6d ago

@futzle Let us know in about 7 hours if the bug fixed itself or not.

@ygor Yeah it’s fine now that the post has gone from 9.997 years old to 10.001 years old.

Borris 6d ago

@futzle @dgar I am glad to not have been the only one who noticed that.

Simon Zerafa (Status:

😊)6d ago

@futzle

The message age field really needs to be a float rather than an int. It probably should have been shown as 9.99995 years or similar 🙂

MBEverding 6d ago

@futzle Bug Not on tusky (also I'm in German CET time)

MBEverding 6d ago

@futzle post cannot even be displayed on #brutaldon #kaios

^[[200~Michael 6d ago

@futzle If temporal can't fix this it's DOA to me /s

Jordi (Tubal Hippy)6d ago

@futzle

It wouldn't be the Fediverse is there wasn't some fucking bug 🤣

schratze 6d ago

@futzle this is why absolute timestamps are better than relative ones in every conceivable way.

Ben Harris-Roxas 6d ago

@futzle lol

@futzle I am constantly finding weird annoying things like that in the Python date humanizer that I use and it's so frustrating, especially when I explain why the behavior could be better and they go off and "fix" it in an even more baffling way

Programmers really are bad at understanding intuition vs. The Numbers

@fluffy Python has a Special way of processing time zones and datetimes which, coming from other languages, I find to be peculiar. Those born into Python can’t see it; indeed, there’s a 50% chance that a Python programmer will come into our mentions to tell me I misunderstand something that I really don’t.

@futzle Yeah. arrow fixes most of the problems with time in Python, but that's where I use the humanizer from and they do such baffling things with how they opt to round dates, and they overthink things like week boundaries when doing it. https://github.com/arrow-py/arrow/issues/1240 for example

Strange `humanize` intervals · Issue #1240 · arrow-py/arrow

Issue Description It seems that the intervals being used for the various thresholds for humanize are a bit strange. For example, on one of my websites, I have a list of upcoming events with both th...

GitHub

@futzle like I wish programmers would think about what different things mean in a colloquial way and it's so baffling that they're not just, like, using humanistic ideas of what time intervals mean

@fluffy It feels to me that everyone is bad about this. This may be an opportune time to refer to the “every other day” “four times a week” hellthread. https://web.archive.org/web/20240131220003/https://forum.bodybuilding.com/showthread.php?t=107926751

Workout Programs

The most popular bodybuilding message boards!

Bodybuilding.com

@futzle haha I remember that, oh god