diff options
Diffstat (limited to '_posts/2023-08-17-25-hour-time.md')
| -rw-r--r-- | _posts/2023-08-17-25-hour-time.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2023-08-17-25-hour-time.md b/_posts/2023-08-17-25-hour-time.md index 477b6dd..da97d6f 100644 --- a/_posts/2023-08-17-25-hour-time.md +++ b/_posts/2023-08-17-25-hour-time.md @@ -24,7 +24,7 @@ If you say "I wrote this sentence on 2023-08-16 at 229x", people will only have ## Completely Missing the Point of Everything -But this is Cohost, and we are no strangers to goofy time notation here. I am not, myself, a .beat time enjoyer, but I know it's a feature and I think it's got several users at varying levels of irony. One of the main things I don't like about .beat time is that it also alienates you from the current date, but we're aggressively solving that in other notations, so can we solve it here too? +But this [was originally, RIP] Cohost, and we are no strangers to goofy time notation here. I am not, myself, a .beat time enjoyer, but I know it's a feature and I think it's got several users at varying levels of irony. One of the main things I don't like about .beat time is that it also alienates you from the current date, but we're aggressively solving that in other notations, so can we solve it here too? 25-hour time demonstrates that it can make sense to reach past the bounds of the time system to express times past the edge of the calendar date; there is no authority who can stop us from doing the same thing to .beat time. I'm writing this on 2023-08-16 at @1400 (which mere mortals might write 2023-08-17 @400). |