Not a bad idea at all. I'm sure we can tackle that. I actually played around with another concept as well which is using the Sun's location as our reference instead of UTC. This then gives our solar system a unified time, not only Earth. It's an incomplete concept still. I have it here in this blog post https://medium.com/adventures-in-consumer-technology/introdu...
Would love to hear what you think.
Thanks for the link, I just read it. Like hTime, there are some potential psychological show-stoppers but I feel like there’s a solid focus on using the very things that time were supposed to be based on.
The problem with date + hTime is that it doesn't have a well defined midnight. Where each 'actual timezone' crosses into the next hTime day is at a different hTime letter. How confusing!
GeoNames (http://www.geonames.org/) offers a downloadable database of cities with more than 15k population and their time zones. They list aliases as well. That's what Zeitzono uses. Just use that.
(You don't have to use all the listed cities if it slows down the hTime web app, just pick some minimum population threshhold (eg. every city larger than 100k people) and use those.)
Thanks for the feedback! As for the list of cities, I'll work on simplifying that somehow. The map idea is pretty cool, it'll take a bit longer to implement. I'll be working on that soon.
True, but not for all events. For example, webinars or global events like SpaceX's launch or the Olympics games. If a game starts at 2pm Tokyo time, I have no direct clue what that could be in my local time. If the game starts at N:00, then I know in my mind what that is.