6 ms·

Nepal is broken (it’s 45 minute offset from norm) I create a meeting Friday at B:00. Is that Thursday or Friday in Sydney? In anchorage? T:00 on Thursday wou

Nepal is broken (it’s 45 minute offset from norm) I create a meeting Friday at B:00. Is that Thursday or Friday in Sydney? In anchorage? T:00 on Thursday would be in about 7 hours from now for someone in Auckland, but in 31 hours for someone in San Francisco. What about a meeting that occurs at 10am local time in New York every day? What happens when the clock changes. The reason to schedule meetings to a timezone is to account for clock changes, otherwise we could just use UTC and be far less confusing that’s this.

quickthrower2 5y ago
Fun fact: my local vaccination centre used Nepal time clock as the “minutes” part for a clock that was 15 minutes slow. Why? That clock showed you the vaccination time that was now safe to leave, having been observed for 15 minutes.
- hhebbo 5y ago
  That's an interesting use case! :)
  - quickthrower2 5y ago
    Yep I appreciated the “geek” that hacked that up. I hope there was some humour behind it. The “normal” thing would be to get a wall clock and wind it back 15!
valray 5y ago
Intentions are good, but I found this system confusing and not useful for me. I use to use Everytimezone, but find Dateful's dual timezone display more useful for my needs. https://dateful.com/time-zone-converter https://dateful.com/time-zone-converter Edit: Added positive remark about good intentions.
- hhebbo 5y ago
  Thanks for the feedback, I appreciate it! May I ask why do you find it confusing? I’d love to improve it.
jmcs 5y ago
It's like UTC but worse. If people need to learn something new, it's better to teach the basics of ISO 8601 to everyone.
hhebbo 5y ago
Well, the clock is UTC. That's the whole concept :) The clock simply combines our local times with UTC in one clock face. To make UTC work for all time zones, it also rotates UTC according to your location on Earth. This means that the reading of time is the same everywhere at any time using the rotated UTC. The clock's algorithm also automatically takes care of all time changes, keeping the reading of time consistent globally. We actually can't just use UTC as is and eliminate time zones completely. If we do so, people in some places would go to work at 2am, in other places at 8pm. That's even more confusing. So the clock of hTime aims to use the best of both local and global times worlds in one clock interface. As for day-changing, I hear you. Again this is UTC, so what the day of UTC is is the day of hTime. Something to work more on indeed.
- Kwpolska 5y ago
  > We actually can't just use UTC as is and eliminate time zones completely. If we do so, people in some places would go to work at 2am, in other places at 8pm. That's even more confusing. If we adopt hTime, people in some places would go to work at C:00, and in other places at U:00. What’s the difference, really? If you say that people in London think that 8-4 UTC (now 9-5 BST) are working hours and would be confused their NYC colleagues would say they are working 4-12 (now 9-5 EDT), then you get the same “confusion” if London thinks I-Q and NYC says N-V.
  - hhebbo 5y ago
    You're right :) The concept is to use both together. And that's what the clock is doing. It keeps local times, and adds UTC as a global time, then maps them together with location-offset-based rotating.
    - jimmydorry 5y ago
      Have you thought about including an additional identifier for the day too? That might help in addressing the edge cases that fall on different days.
      - 5y ago
hhebbo 5y ago
For the info, I just fixed the time zone offset for Nepal in the algorithm. Check it out here https://thehtime.com/location?name=Nepal+-+Kathmandu https://thehtime.com/location?name=Nepal+-+Kathmandu and please let me know if it works.

quickthrower2 5y ago

Fun fact: my local vaccination centre used Nepal time clock as the “minutes” part for a clock that was 15 minutes slow. Why? That clock showed you the vaccination time that was now safe to leave, having been observed for 15 minutes.

hhebbo 5y ago
That's an interesting use case! :)
- quickthrower2 5y ago
  Yep I appreciated the “geek” that hacked that up. I hope there was some humour behind it. The “normal” thing would be to get a wall clock and wind it back 15!

valray 5y ago

Intentions are good, but I found this system confusing and not useful for me. I use to use Everytimezone, but find Dateful's dual timezone display more useful for my needs. https://dateful.com/time-zone-converter https://dateful.com/time-zone-converter Edit: Added positive remark about good intentions.

hhebbo 5y ago
Thanks for the feedback, I appreciate it! May I ask why do you find it confusing? I’d love to improve it.

jmcs 5y ago

It's like UTC but worse. If people need to learn something new, it's better to teach the basics of ISO 8601 to everyone.

hhebbo 5y ago

Well, the clock is UTC. That's the whole concept :) The clock simply combines our local times with UTC in one clock face. To make UTC work for all time zones, it also rotates UTC according to your location on Earth. This means that the reading of time is the same everywhere at any time using the rotated UTC. The clock's algorithm also automatically takes care of all time changes, keeping the reading of time consistent globally. We actually can't just use UTC as is and eliminate time zones completely. If we do so, people in some places would go to work at 2am, in other places at 8pm. That's even more confusing. So the clock of hTime aims to use the best of both local and global times worlds in one clock interface. As for day-changing, I hear you. Again this is UTC, so what the day of UTC is is the day of hTime. Something to work more on indeed.

Kwpolska 5y ago
> We actually can't just use UTC as is and eliminate time zones completely. If we do so, people in some places would go to work at 2am, in other places at 8pm. That's even more confusing. If we adopt hTime, people in some places would go to work at C:00, and in other places at U:00. What’s the difference, really? If you say that people in London think that 8-4 UTC (now 9-5 BST) are working hours and would be confused their NYC colleagues would say they are working 4-12 (now 9-5 EDT), then you get the same “confusion” if London thinks I-Q and NYC says N-V.
- hhebbo 5y ago
  You're right :) The concept is to use both together. And that's what the clock is doing. It keeps local times, and adds UTC as a global time, then maps them together with location-offset-based rotating.
  - jimmydorry 5y ago
    Have you thought about including an additional identifier for the day too? That might help in addressing the edge cases that fall on different days.
    - 5y ago

hhebbo 5y ago

For the info, I just fixed the time zone offset for Nepal in the algorithm. Check it out here https://thehtime.com/location?name=Nepal+-+Kathmandu https://thehtime.com/location?name=Nepal+-+Kathmandu and please let me know if it works.