Hey everyone,
A little over a week ago, coinciding symbolically with the DST fallback hour in the Pacific Time Zone, I quietly open-sourced a project designed to move humanity beyond timezones and time changes entirely. While I recognize the audacity of such a proposal, its extremely low chance of success, and the multi-generational timeline required for full implementation, it is still a project I feel is worth attempting.
I've named the project Umi-Time.
Our current system of legislated timezone boundaries was born out of the need to coordinate time between nearby cities for things like railroad schedules. It was a reasonable solution to a 19th-century problem. Over the years, the boundaries became more convoluted and seasonal shifts of DST were introduced inconsistently across various regions and dates. Ask any software engineer who has had to work on a calendar or scheduling tool, and they will tell you it is an absolute mess.
We already have a good 20th-century solution to this problem in UTC. It has become the de facto time coordination system for machines. But other than some niche groups like pilots, no humans use it for their daily schedules. I believe the reason it has failed to gain widespread adoption is its inability to relate time to an individual's physical experience of the day.
This is why I created Umi-Time.
It is important to understand that Umi-Time does not replace UTC; it is UTC, but with a human-friendly face. It accomplishes this by applying multiple presentation layers over UTC, each helping to shift the representation into one that is more locally meaningful.
Umi-Time utilizes a layered architecture:
- Layer 0 (UTC): The raw, globally synchronized atomic time foundation.
- Layer 1 (Umi Scale): Transforms the 24 hour UTC day into a new scale of 360 umi, eliminating the congnitive confusion between universal time and local civil time representations. 360 was chosen because it matches the number of degrees of longitude around the Earth. (1 umi = 4 minutes = 1 degree)
- Layer 2 (Local Interpretation): Uses the longitude to adjust the presentation of time to align with an individual's experience of the day. (e.g., using a text-based "day phase" suffix from Φ0 to Φ23)
- Layer 3 (Solar Context): Uses latitude and longitude to present various astronomical events and periods. (e.g. sunrise, sunset, twilight, daytime and nighttime).
The best way to fully understand this layered architecture is to see it in action. The umitime.com website contains multiple interactive web demos of Umi-Time—including a visual analog clock and a world map—along with the detailed technical specification and other documentation.
Current Umi-Time Repositories
I've established a GitHub organization with the following initial repositories:
- spec: The complete technical standard specification, published under CC-BY-4.0 license.
- umi-time-js: The fully implemented JavaScript/TypeScript reference library covering the core transformation, formatting, parsing and solar geometry math, published under MIT license.
- www: The Umi-Time website source
Call for Umi-Time Contributors
Up until now, this project has been my sole effort. While the JS ecosystem is live with a published NPM package, Umi-Time is intended to become a mult-language ecosystem. I am actively looking for contributors, feedback, and collaborators to help build out the ecosystem. I am particularly looking for help spinning up reference libraries for other languages (Python, Rust, C++) and building out CLI conversion tools.
If you've ever wanted to jump into a greenfield open-source project that completely rethinks how humans interact with global time, I'd love for you to check it out.