News for hackers. Stuff that matters.
Re:Show HN: A new clock to eliminate time zone calculations ... by hhebbo on Monday October 18, 2021 @10:03AM (#28905527)
thanks for the feedback. You're right, and I have a solution for that already. Check this link https://thehtime.com/intersect?locations=USA+-+San+Francisco...

I have a feature for meeting planning. The clock then finds the best time for a meeting between the different location without the need to do any calculations on your end, or the other attendees' ends. With this feature, you can also choose the working hours availability. In the link above it shows the best time for a meeting between San Francisco, London, and Berlin for working availability between 8am and 7pm for everyone.

The idea is eliminate the calculations, and the confusing names of all time zones and daylight saving.

Re:Show HN: A new clock to eliminate time zone calculations ... by linkdd on Monday October 18, 2021 @10:36AM (#28905840)
I already use calendly.com or savvycal.com for this purpose. I only need to think about my time zone.

On another note, how would you store your datetime in a database? If I understand correctly, we would need to save the location as well, so no real difference with a datetime+locale.

Am I missing something?

Re:Show HN: A new clock to eliminate time zone calculations ... by hhebbo on Tuesday October 19, 2021 @06:23PM (#28924526)
calendly and savvycal are mainly calendar apps and work well for the scheduling use case only. However, this is only one use case that a global clock can be used for. Another use case that those apps don't solve is global events e.g. SpaceX launching a rocket at 11am ET, or the Apple event yesterday at 10am PDT. If I don't live in those time zones, I don't know when those events are going to take place in my time. Thus the idea of eliminating time zones and replacing that with a global clock would solve many more use cases than scheduling.

There is no need to store datetime or locale for the clock to work. The clock knows where you are, using your sys time, or GPS, and according to that it rotates the UTC layer that is represented in letters according to you location. This means the clock adjusts itself for you in order to give the right local-global (UTC) time mapping. And that's all done by the clock's algorithm that manages the rotation. The main reason I'm using letters instead of numbers for UTC is to distinguish between local and global hours, simply for better communication.

That's how it works :)