5 ms·

Honest q I hope doesn't sound rude: how is this different from @beat swatch time? Looks really nice and I hope you and your process success, you're fixing a pr

Honest q I hope doesn't sound rude: how is this different from @beat swatch time? Looks really nice and I hope you and your process success, you're fixing a problem

throw_away 5y ago
@beat was a full decimalization of time (1000 'beats' per day). This is just giving new, universal names to hours. I can see this working a lot better than the alternative (use GMT/UTC everywhere) as you'd always have mental contention as to whether you meant a time in local or GMT. This way you don't need the additional label. And I could imagine getting used to the idea that my workday lasted from P-X & the other geographical zones had their common hour blocs. Potential issues: * 0/O ambiguity * presumably the day flips over when the hour goes from X->A, which means sometimes it's tomorrow already.
- hhebbo 5y ago
  Thanks for the clarification and feedback! As for the issues: - 0/O: I just fixed that by excluding I & O, and adding Y & Z. - Correct
hhebbo 5y ago
Not at all, thanks for asking and the nice wishes ;) The Internet Time, Beats, is a completely new time/clock system. It’s unclear what 964 for example means. With this clock, I’m using the same time/clock system we all know well: 24 hours, 60 minutes, 60 seconds. The addition to that is UTC. Why? To make the clock show the global time as well, and then map the local time with the global time together in one clock face. By this, we can always be in sync locally and globally. The UTC layer in the middle is represented by letters to simply distinguish global from local times. This layer rotates with users according to their location on Earth. Why? To unify the reading of time when doing the mapping, so the reading of time is always the same no matter where users are. I understand that the letters might be confusing a bit, but this can be fixed easily by replacing them with numbers again. Here is an example: 2 days ago there was the Apple event. It was at 10am PDT. I’m not sure what that is in my local time and other local times. If that event would be translated to hTime, it would be at R:00. No matter where we are, we can see the local and global hours for R:00, so no time zone calculations are needed any more. I believe the barrier-to-entry with a 24-hour, 60-minute, 60-second system is simpler than Beat.

Honest q I hope doesn't sound rude: how is this different from @beat swatch time? Looks really nice and I hope you and your process success, you're fixing a problem

throw_away 5y ago

@beat was a full decimalization of time (1000 'beats' per day). This is just giving new, universal names to hours. I can see this working a lot better than the alternative (use GMT/UTC everywhere) as you'd always have mental contention as to whether you meant a time in local or GMT. This way you don't need the additional label. And I could imagine getting used to the idea that my workday lasted from P-X & the other geographical zones had their common hour blocs. Potential issues: * 0/O ambiguity * presumably the day flips over when the hour goes from X->A, which means sometimes it's tomorrow already.

hhebbo 5y ago
Thanks for the clarification and feedback! As for the issues: - 0/O: I just fixed that by excluding I & O, and adding Y & Z. - Correct

hhebbo 5y ago

Not at all, thanks for asking and the nice wishes ;) The Internet Time, Beats, is a completely new time/clock system. It’s unclear what 964 for example means. With this clock, I’m using the same time/clock system we all know well: 24 hours, 60 minutes, 60 seconds. The addition to that is UTC. Why? To make the clock show the global time as well, and then map the local time with the global time together in one clock face. By this, we can always be in sync locally and globally. The UTC layer in the middle is represented by letters to simply distinguish global from local times. This layer rotates with users according to their location on Earth. Why? To unify the reading of time when doing the mapping, so the reading of time is always the same no matter where users are. I understand that the letters might be confusing a bit, but this can be fixed easily by replacing them with numbers again. Here is an example: 2 days ago there was the Apple event. It was at 10am PDT. I’m not sure what that is in my local time and other local times. If that event would be translated to hTime, it would be at R:00. No matter where we are, we can see the local and global hours for R:00, so no time zone calculations are needed any more. I believe the barrier-to-entry with a 24-hour, 60-minute, 60-second system is simpler than Beat.