aboutsummaryrefslogtreecommitdiff
path: root/_posts/2023-08-17-25-hour-time.md
diff options
context:
space:
mode:
authorMelody Horn <melody@boringcactus.com>2025-04-13 11:05:14 -0600
committerMelody Horn <melody@boringcactus.com>2025-04-13 11:05:14 -0600
commite271f32674f91c1fdaaad83edbbf4491c24b405c (patch)
tree566f896328f16196b9592e9c8e9db642ad46dba4 /_posts/2023-08-17-25-hour-time.md
parentbde494cb7361748a010aae9b1bdfa1e68fb42285 (diff)
downloadboringcactus.com-e271f32674f91c1fdaaad83edbbf4491c24b405c.tar.gz
boringcactus.com-e271f32674f91c1fdaaad83edbbf4491c24b405c.zip
rip cohost
Diffstat (limited to '_posts/2023-08-17-25-hour-time.md')
-rw-r--r--_posts/2023-08-17-25-hour-time.md2
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).